chore: migrate to Release-Please + reusable workflows#70
Open
TheMeinerLP wants to merge 2 commits into
Open
Conversation
Adopt the OneLiteFeather engineering standard (gold master: Cygnus): - add release-please-config.json + .release-please-manifest.json (v0.9.1) - add .github/workflows/release-please.yml (release-please-action@v5), publishing via reusable OneLiteFeatherNET/workflows gradle-publish.yml@v2.4.0 - build-pr.yml now calls reusable gradle-build-pr.yml@v2.4.0 - close_invalid_prs.yml now calls reusable close-invalid-prs.yml@v2.4.0 (protected-branch: develop) - annotate version in build.gradle.kts for release-please generic updater - remove superseded main-build.yml, publish.yml, release-drafter.yml
TheMeinerLP
force-pushed
the
chore/release-please-migration
branch
from
e731528 to
36a18eb
Compare
Test results 9 files 9 suites 0s ⏱️ Results for commit b1544ba. ♻️ This comment has been updated with latest results. |
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
2 participants
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.
Pilot migration to the OneLiteFeather engineering standard (gold master: Cygnus), covering both Release-Please and the reusable workflows.
What changed
release-please-config.json(release-type: simple,include-v-in-tag: falseto match existing0.9.xtags,bootstrap-shapinned to current develop HEAD).release-please-manifest.json→0.9.1.github/workflows/release-please.ymlusinggoogleapis/release-please-action@v5, publishing on release via reusablegradle-publish.yml@v2.4.0(publish-task: publish)build.gradle.ktsannotated with// x-release-please-versionso the generic updater bumps itbuild-pr.yml→OneLiteFeatherNET/workflows/.github/workflows/gradle-build-pr.yml@v2.4.0close_invalid_prs.yml→close-invalid-prs.yml@v2.4.0(protected-branch: develop)main-build.yml,publish.yml,release-drafter.ymlBehavior notes
develop(no more tag-triggeredpublish.yml, no more release-drafter).X.Y.Z(novprefix), consistent with existing tags.