Skip to content

Conversation

shortcuts
Copy link
Member

🧭 What and Why

🎟 JIRA Ticket: -

Changes included:

The next Java version seems incorrectly bumped in #653, this PR adds a small edge case to bump the version normally but keep the -SNAPSHOT.

🧪 Test

CI :D

@shortcuts shortcuts requested review from eunjae-lee and millotp June 8, 2022 13:09
@shortcuts shortcuts self-assigned this Jun 8, 2022
@netlify
Copy link

netlify bot commented Jun 8, 2022

Deploy Preview for api-clients-automation canceled.

Name Link
🔨 Latest commit 6be3bf6
🔍 Latest deploy log https://app.netlify.com/sites/api-clients-automation/deploys/62a0a3a18f8e6e000b888121

@algolia-bot
Copy link
Collaborator

algolia-bot commented Jun 8, 2022

✗ The generated branch has been deleted.

If the PR has been merged, you can check the generated code on the main branch.
You can still access the code generated on main via this commit.

@shortcuts shortcuts requested a review from millotp June 8, 2022 13:36
@shortcuts shortcuts enabled auto-merge (squash) June 8, 2022 13:42
Copy link
Collaborator

@millotp millotp left a comment

Choose a reason for hiding this comment

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

nice !

@shortcuts shortcuts merged commit c3b4f1c into main Jun 8, 2022
@shortcuts shortcuts deleted the chore/fix-version-bump-java branch June 8, 2022 13:47
...version,
releaseType: 'patch',
...(commitTypes.has('fix') ? undefined : { skipRelease: true }),
next: getNextVersion(currentVersion, 'patch'),
Copy link
Contributor

Choose a reason for hiding this comment

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

why do we include next here, while we can compute it anywhere based on currentVersion and releaseType?

Copy link
Member Author

Choose a reason for hiding this comment

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

Oops sorry I had auto merge on.

It was previously computed at the changelog creation level, I've put it a level above as this is where the releaseType is computed. Do you think there's a better place for it?

Copy link
Contributor

Choose a reason for hiding this comment

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

A bit of history FYI, I avoided to add next version there especially because JS actually have independent versions.

Copy link
Member Author

Choose a reason for hiding this comment

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

I've made sure here it still follows the same logic: #656

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants