Repository navigation
Release on a merged version bump, a tag, or by hand - #145
Merged
Merged
Conversation
release.yml ran only on a pushed v* tag. It now also runs when a push to main changes bibliography-builder.php or the workflow, and by workflow_dispatch. It reads the version from the plugin header, fails unless readme.txt, package.json and block.json agree, and does nothing when that version's release already exists; otherwise it creates the tag with the release and dispatches wp-deploy.yml on it, as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019tRjxfxyEhwi8RhyrD8Vvk
Merged
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #145 +/- ##
=========================================
Coverage 87.87% 87.87%
Complexity 22 22
=========================================
Files 59 59
Lines 6952 6952
Branches 678 678
=========================================
Hits 6109 6109
Misses 292 292
Partials 551 551 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.
Why
Borges releases only when a
v*tag is pushed. This brings it in line with Byline Feed (dknauss/author-identity#65, #66): merging a version bump releases it.What
release.ymlnow runs on any of:v*tag (the tag must match the plugin version);mainthat changesbibliography-builder.phpor the workflow;workflow_dispatch).It reads the version from the plugin header. It fails unless the
readme.txtStable tag,package.jsonandblock.jsonall agree. If a release for that version already exists, it stops there. Otherwise it builds, packages, extracts the CHANGELOG section, and creates the release at this commit, which creates the tag. It then dispatcheswp-deploy.ymlon that tag, as before.Merging this PR changes nothing: the workflow runs, finds the v1.10.0 release, and stops.
Docs: the CLAUDE.md release and CI notes, plus
docs/release-readiness-checklist.md, which now tells you to run the checklist before merging the bump, because the merge publishes it. The release-workflow Jest tests are updated, with a new one for the triggers.Checks
npm test -- src/release-workflows.test.js: 7 tests pass.🤖 Generated with Claude Code
https://claude.ai/code/session_019tRjxfxyEhwi8RhyrD8Vvk
Generated by Claude Code