Skip to content
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

Release v0.5.1 #32

Merged
merged 1 commit into from
Jun 15, 2021
Merged

Release v0.5.1 #32

merged 1 commit into from
Jun 15, 2021

Conversation

aurelien-reeves
Copy link
Contributor

See diff for details.

@mattwynne mattwynne merged commit 841c4bf into release Jun 15, 2021
@mattwynne mattwynne deleted the release-v0.5.1 branch June 15, 2021 06:39
@mattwynne
Copy link
Member

@aurelien-reeves as far as I'm concerned, you don't need to wait for someone else to approve a release PR; you can release it yourself.

mattwynne added a commit that referenced this pull request Jul 28, 2021
* Release v0.5.1 (#32)

* Release v0.5.2

* Add Dart (#36)

* Add Dart installation to main image
* Update changelog

Used an adapted version of the script from dart-lang/sdk#26953 (comment) to work on x64 and arm64 architectures.

* use nodejs 14 (#37)

* use nodejs 14

* Update CHANGELOG.md

* Added a pre-release workflow

This workflow is designed to automatically create a PR to the release
branch when the CHANGELOG is updated.

* Release 0.6.0

* try something else

* Revert "Release 0.6.0"

This reverts commit 57f341d.

* Release 0.6.0

* Try checking out release first

* Revert "Release 0.6.0"

This reverts commit 4d106cf.

* Fix yaml syntax

* Release 0.6.0

* Try as separate commands

* Revert "Release 0.6.0"

This reverts commit 16c6789.

* Release 0.6.0

* Revert "Release 0.6.0"

This reverts commit 5f8b1da.

* Release 0.6.0

* Try not committing the release stuff to main yet.

We can merge it back down to main once the release is done.

* Revert "Release 0.6.0"

This reverts commit a9dc1b6.

* Use a different branch naming strategy

* Try using release branch again

* Follow the steps in the README to create the branch

* Also checkout main

* Use proper ref for main

* Try git commands by hand

* Name the committer

* Correct name for branch

* I think we can let the GH action do the commit

* Push the new branch?

* Better push

* Fix typo

* Fix bad merge

* Let PR action create branch

* Read current release version from git tags

* Fetch tags

* Better job name

* Repair changelog - 0.6.0 has not been released yet!

* Try to trigger pre-release for 0.6.0 again

* Trigger pre-release

* Tweak working in release PR

Co-authored-by: Aurélien Reeves <aurelien.reeves@smartbear.com>
Co-authored-by: David Goss <david@davidgoss.co>
Co-authored-by: Matt Wynne <matt@cucumber.io>
Co-authored-by: mattwynne <mattwynne@users.noreply.github.com>
mattwynne pushed a commit that referenced this pull request Jul 28, 2021
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.

None yet

2 participants