Skip to content

Ready for release #62

Open
Open

Description

@vlazzarini

Repository reorganised. We are now ready for release, two things required

  • release tagging and versioning needs to be resolved (not sure if workflows need to be adjusted for this).
  • a PR against main with the 'release' label should trigger a release (as in csound/csound), worth a check.

@hlolli what do you reckon?

Activity

  1. hlolli commented on Oct 29, 2026

    @hlolli
    Member

    @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.

  2. linked a pull request that will close this issueRelease 7.0.0 #64on Oct 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions