Conversation
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 7. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v4...v7) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 6. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v4...v6) --- updated-dependencies: - dependency-name: actions/setup-node dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
…tions/checkout-7 ci: Bump actions/checkout from 4 to 7
…tions/setup-node-6 ci: Bump actions/setup-node from 4 to 6
PR #3 landed the GitHub Actions version bumps on `main` via its own commits; `dev` already had the same bumps from Dependabot (#1, #2). Merging main back into dev reconciles the two histories (no file changes — trees are identical) so future dev->main release merges have a clean base. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
chore: sync dev with main after PR #3 (git-flow back-merge)
…ANGELOG - release.yml: trigger on push to `main`; read version from manifest.json and, if not already released, push the bare-version tag and publish the release in the same job. Idempotent — version-less merges (CI/docs) are a no-op. Removes the manual tag-push step. - Add a named release PR template (.github/PULL_REQUEST_TEMPLATE/release.md) for dev->main release PRs. - Add CHANGELOG.md (Keep a Changelog) with the 1.1.1 entry. - CONTRIBUTING: rewrite the releasing section for the automatic flow. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
ci: auto-tag & release on merge to main; add release PR template + CHANGELOG
3 tasks
jphan32
added a commit
that referenced
this pull request
Jun 23, 2026
chore: back-merge main into dev (sync after PR #6)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Sync
dev → mainto activate the automatic release pipeline onmain.This is not a version release —
manifest.jsonstays at1.1.1.Brings to
mainthe changes already integrated ondev:release.yml— the reworked workflow that auto-tags and releases on push tomain(reads the version frommanifest.json; idempotent — skips when thatversion is already released).
.github/PULL_REQUEST_TEMPLATE/release.md— the release PR template.CHANGELOG.md— Keep a Changelog, seeded with1.1.1.CONTRIBUTING.md— releasing section rewritten for the automatic flow.Release-safety of this merge
The new
release.ymlruns on the very push that lands it onmain. It readsmanifest.json→1.1.1, which is already released, so the guard short-circuits and no tag or release is created. From the next version-bumping
dev → mainmerge onward, releases happen automatically.Type of change
Checklist
main.js/styles.csschange;manifest.jsonversion unchanged (1.1.1)