Skip to content

docs: publish a GitHub release as the last release step #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
timbenniks-contentstack merged 3 commits into from
Oct 23, 2026
Merged

docs: publish a GitHub release as the last release step #28

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
491d6a9
docs: tag and publish a GitHub release as the last release step
timbenniks-contentstack Oct 23, 2026
ebaae8f
Merge pull request #27 from contentstack/docs/release-checklist
timbenniks-contentstack Oct 23, 2026
184cb2c
Merge branch 'main' into next
timbenniks-contentstack Oct 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/contributing/release-and-versioning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ There are no generated artifacts, so any validated commit on `main` is a coheren
3. Add a section for the new version to [`CHANGELOG.md`](../../CHANGELOG.md), calling out renamed or removed skills.
4. Run `node scripts/validate.mjs`.
5. Confirm CI passes on the pull request.
6. Merge to `main` and tag the release.
6. Merge to `main`, tag `vX.Y.Z` on the merge commit, and publish a GitHub release whose notes are the version's `CHANGELOG.md` section.

## How updates reach users

Expand Down
Loading