Skip to content

chore: prepare release 2022-06-21 #728

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 2 commits into from
Jun 21, 2022
Merged

Conversation

damcou
Copy link
Contributor

@damcou damcou commented Jun 21, 2022

Summary

This PR has been created using the yarn release script. Once merged, the clients will try to release their new version if their version has changed.

Version Changes

  • javascript: 0.5.0 -> patch (e.g. 0.5.1)
  • java: 4.1.0-SNAPSHOT -> minor (e.g. 4.2.0-SNAPSHOT)
  • php: 4.0.0-alpha.1 -> prerelease (e.g. 4.0.0-alpha.2)

Skipped Commits

It doesn't mean these commits are being excluded from the release. It means they're not taken into account when the release process figured out the next version number, and updated the changelog.

Commits without language scope:
Commits with unknown language scope:

@damcou damcou requested review from a team, millotp and shortcuts and removed request for a team June 21, 2022 08:38
@netlify
Copy link

netlify bot commented Jun 21, 2022

Deploy Preview for api-clients-automation canceled.

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

@algolia-bot
Copy link
Collaborator

algolia-bot commented Jun 21, 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.

@damcou damcou merged commit b831501 into main Jun 21, 2022
@damcou damcou deleted the chore/prepare-release-2022-06-21 branch June 21, 2022 09:21
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.

3 participants