feat: 187 automatically create new release each time a json schema change is merged #189
Conversation
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
jcpitre
reviewed
Dec 23, 2025
| name: Auto Release on Schema Changes | ||
|
|
||
| on: | ||
| pull_request: |
Contributor
There was a problem hiding this comment.
Did you consider using a push to master trigger instead?
See this as an example
One advantage is that you can restrict the trigger only to changes in specified folders.
Contributor
Author
There was a problem hiding this comment.
Yes — using a push trigger with paths would work, but I opted for a pull_request: closed trigger to ensure releases only happen after an explicit PR merge and to avoid accidental releases from direct pushes.
jcpitre
approved these changes
Dec 24, 2025
qcdyx
deleted the
187-automatically-create-new-release-each-time-a-json-schema-change-is-merged
branch
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.
Tested locally using git diff --name-only against simulated PR diffs, and end-to-end by merging test-release PR into 187-automatically-create-new-release-each-time-a-json-schema-change-is-merged. Verified that releases are created when new root-level vX.X folders are added or when existing vX.X schemas change, and not created for non-schema changes.
p.s. I already deleted Release 4.1.0, should have used pre-release.