Skip to content

RELEASING.md

Latest commit

 

History

History
39 lines (29 loc) · 973 Bytes

RELEASING.md

File metadata and controls

39 lines (29 loc) · 973 Bytes

Releasing

Version Strategy

  • v1.0.0, v1.1.0, etc. - Semantic versions for changelogs
  • v1 - Floating tag that always points to latest v1.x.x
  • v2 - Breaking changes warrant a new major version

Release Process

  1. Make changes and push to main

  2. Tag the release:

    git tag v1.x.x
git push origin v1.x.x

  3. Automated steps (via .github/workflows/release.yml):

    • Creates GitHub Release with auto-generated notes
    • Updates floating v1 tag to point to new version

  4. Publish to Marketplace (manual, one-time per major version):

    • Edit the release on GitHub
    • Check "Publish this Action to the GitHub Marketplace"
    • Select categories: "Continuous Integration", "Utilities"
    • Save

Testing Before Release

Test changes by referencing the branch:

uses: NimbleBrainInc/mcpb-pack@my-feature-branch

Or reference a specific commit:

uses: NimbleBrainInc/mcpb-pack@abc123