Skip to content

chore(ci): add versioning workflow for pre-release #2006

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 12 commits into from
Feb 6, 2024

Conversation

am29d
Copy link
Contributor

@am29d am29d commented Feb 2, 2024

Description of your changes

This PR adds a workflow to run versioning before a release, which solves two issues. 1/ lerna version does not push the commit back to main, 2/ we can review version and changelog changes before the release, avoiding accidentally wrong version bumps based on conventional commits.

While we previously had a tag during versioning, I suggest keeping the tag after a successful package publish step in the release workflow.

Related issues, RFCs

Issue number: #1799

Checklist

  • My changes meet the tenets criteria
  • I have performed a self-review of my own code
  • I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my change is effective and works
  • The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

  • I have documented the migration process
  • I have added, implemented necessary warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Sorry, something went wrong.

Verified

This commit was signed with the committer’s verified signature.
am29d Alexander Schueren
@am29d am29d requested a review from a team February 2, 2024 09:25
@boring-cyborg boring-cyborg bot added the automation This item relates to automation label Feb 2, 2024
@pull-request-size pull-request-size bot added the size/L PRs between 100-499 LOC label Feb 2, 2024
@am29d am29d requested review from sthulb and dreamorosi February 2, 2024 09:25
@am29d am29d self-assigned this Feb 2, 2024
am29d added 4 commits February 2, 2024 15:11

Verified

This commit was signed with the committer’s verified signature.
am29d Alexander Schueren

Verified

This commit was signed with the committer’s verified signature.
am29d Alexander Schueren

Verified

This commit was signed with the committer’s verified signature.
am29d Alexander Schueren

Verified

This commit was signed with the committer’s verified signature.
am29d Alexander Schueren
am29d added 3 commits February 2, 2024 15:29

Verified

This commit was signed with the committer’s verified signature.
am29d Alexander Schueren

Verified

This commit was signed with the committer’s verified signature.
am29d Alexander Schueren

Verified

This commit was signed with the committer’s verified signature.
am29d Alexander Schueren
…LEASE_VERSION
@dreamorosi dreamorosi self-requested a review February 3, 2024 21:50
Copy link
Contributor

@dreamorosi dreamorosi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for working on this. Looks great and I have tested it in a fork.

Would like to hear from @sthulb if we could move this action (aka only what's under .github/actions/create-pr) under the dedicated actions repo we have in the org.

This action is an almost exact copy of the one here from the Python repo. The changes we made here should be able to be refactored so that they're parameters/inputs of the action.

This way we can have a single place & maintain only once rather than have the same / slightly similar action in two projects.

@dreamorosi
Copy link
Contributor

@sthulb what about the question here on moving the action under the actions repo?

am29d added 4 commits February 6, 2024 09:39

Verified

This commit was signed with the committer’s verified signature.
am29d Alexander Schueren

Verified

This commit was signed with the committer’s verified signature.
am29d Alexander Schueren

Verified

This commit was signed with the committer’s verified signature.
am29d Alexander Schueren

Verified

This commit was signed with the committer’s verified signature.
am29d Alexander Schueren
Copy link

sonarqubecloud bot commented Feb 6, 2024

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

Copy link
Contributor

@dreamorosi dreamorosi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for raising the bar on this!

@am29d am29d merged commit b7385dc into main Feb 6, 2024
@am29d am29d deleted the chore/versioning-workflow branch February 6, 2024 15:45
@am29d am29d restored the chore/versioning-workflow branch February 6, 2024 16:08
@dreamorosi dreamorosi linked an issue Feb 9, 2024 that may be closed by this pull request
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation This item relates to automation size/L PRs between 100-499 LOC
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Maintenance: refactor versioning process
3 participants