You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@vlazzarini I think 7.0.0 makes sense for the first Csound 7-only release, keeping the native and npm packages on the same version line.
I've opened #63 against develop to set this up. It uses package.json as the version source for release tags and asset names. A release-labelled PR into main publishes after it merges and all native builds pass. The tag points to that exact merge commit, and the workflow rejects an existing tag that points elsewhere. Labelled merges into develop can still publish prereleases.
Once #63 is merged, we can open the develop → main release PR and add the release label before merging. npm publication stays manual.
Activity
hlolli commentedon Oct 29, 2026
@vlazzarini I think
7.0.0makes sense for the first Csound 7-only release, keeping the native and npm packages on the same version line.I've opened #63 against
developto set this up. It usespackage.jsonas the version source for release tags and asset names. Arelease-labelled PR intomainpublishes after it merges and all native builds pass. The tag points to that exact merge commit, and the workflow rejects an existing tag that points elsewhere. Labelled merges intodevelopcan still publish prereleases.Once #63 is merged, we can open the
develop→mainrelease PR and add thereleaselabel before merging. npm publication stays manual.