ci(DATAGO-113775): introduce versioning and release pipeline #83
+1,639
−0
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
artyom-morozov
force-pushed
the
versioning
branch
from
87146b8 to
7664f79
Compare
| # - release-please-config.json | ||
| # - .github/pr_labeler.yaml | ||
|
|
||
| on: |
Collaborator
There was a problem hiding this comment.
Let's document the process for adding new plugins
I.e PR is opened -> let the sync plugin workflow run -> makes a commit to the PR branch
-> New workflows will run
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.
What is the purpose of this change?
Implement automated release management using Release Please for the monorepo. This enables automatic changelog generation, version bumping, and PyPI publishing for all 16 plugins based on conventional commits.
How was this change implemented?
New Workflows:
release-please.yaml: Runs on push to main, creates/updates release PRs automatically based on conventional commits, manages separate versions for each pluginpublish.yaml: Triggered when GitHub releases are published, builds and publishes the specific plugin to PyPI using trusted publishing (no API tokens needed)release-readiness-check.yaml: Runs on release-please PRs to validate security compliance (SonarQube hotspots, FOSSA licensing/vulnerabilities) before releaseConfiguration Files:
release-please-config.json: Defines release configuration for all 16 plugins with changelog sections, tag format (<plugin>-v<version>), and Python release type.release-please-manifest.json: Tracks current versions for each plugin (initialized to current versions)Key Design Decisions (optional - delete if not applicable)
separate-pull-requests: falseto group all plugin releases into one PR for easier managementsam-slack-v0.3.0) to differentiate releases per plugin