[feat] Automate brownfield gradle plugin releases#351
Open
adamTrz wants to merge 4 commits into
Open
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
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.
Summary
This PR automates Maven Central publication for the Brownfield Gradle Plugin and removes the manual local-zip upload process.
It adds:
brownfield-gradle-plugin/v*tags andworkflow_dispatchWhy
The plugin was previously published manually by signing and publishing to
mavenLocal(), zipping thecom/subtree, and uploading it manually to Maven Central. That flow was slow, error-prone, and had no release-notes automation.Impact
Maintainers can now:
workflow_dispatchdry run that generates notes and stages Maven artifacts without publishinggradle-plugins/react/brownfield/gradle.propertiesDevelopers keep the existing local snapshot path for CI and local Android testing via
mavenLocal().Validation
Validated in an isolated worktree on top of
origin/main.Passed locally:
node --test --experimental-strip-types scripts/__tests__/sync-brownfield-gradle-plugin-version.test.tsnode --test --experimental-strip-types scripts/__tests__/generate-brownfield-gradle-plugin-release-notes.test.tsyarn brownfield:plugin:version:checkyarn brownfield:plugin:release-notes --version 1.1.0 --ref HEAD --output /private/tmp/bgp-release-notes.mdruby -e 'require "yaml"; YAML.load_file(".github/workflows/release-brownfield-gradle-plugin.yml"); YAML.load_file("jreleaser.yml"); puts "yaml ok"'git diff --checkcd gradle-plugins/react && ./gradlew :brownfield:publishMavenLocalPublicationToReleaseStagingRepository -PSkipSigning=trueyarn brownfield:plugin:publish:local:signedcd gradle-plugins/react && ./gradlew :brownfield:publishMavenLocalPublicationToReleaseStagingRepository.ascsignatures for jar, sources jar, javadoc jar, module metadata, and pomtypecheck,lint,commitlintPassed remotely before removing the temporary PR-only trigger used for pre-merge validation:
26442399021on PR#351Validate release inputs and stage artifactspassedPublish Brownfield Gradle Pluginwas skipped intentionallybrownfield-gradle-plugin-release-notesbrownfield-gradle-plugin-staging-repoStill not executed remotely:
workflow_dispatchdry run after merge tomain