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.

Sign up for GitHub

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

Jump to bottom

chore(main): release 0.5.0 #28

Merged
merged 1 commit into from
Aug 19, 2024
Merged

chore(main): release 0.5.0 #28

merged 1 commit into from
Aug 19, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jul 3, 2024 •
edited
Loading

🤖 I have created a release beep boop

0.5.0 (2024-08-19)

Features

  • update CI so it runs on release as well (#33) (4517996)

Bug Fixes

  • re-apply update CI so it runs on release as well (#49) (51d5a43)
  • revert "update CI so it runs on release as well" (#44) (9d0e859)
  • set cookies for password recovery event (#32) (7dc1837)
  • set cookies when mfa challenge is verified (#27) (c217f53)
  • update conventional commits ci to use main instead of master (#31) (bebce89)

This PR was generated with Release Please. See documentation.

@github-actions GitHub Actions
Copy link
Contributor Author

github-actions bot commented Jul 3, 2024

Release candidate v0.4.1-rc.1 published.

@github-actions github-actions bot force-pushed the release-please--branches--main branch from ed4af0a to 3d67993 Compare July 3, 2024 18:40
@github-actions GitHub Actions
Copy link
Contributor Author

github-actions bot commented Jul 3, 2024

Release candidate v0.4.1-rc.2 published.

@github-actions github-actions bot force-pushed the release-please--branches--main branch from 3d67993 to 34680eb Compare July 3, 2024 18:42
@github-actions GitHub Actions
Copy link
Contributor Author

github-actions bot commented Jul 3, 2024

Release candidate v0.4.1-rc.3 published.

@J0 J0 marked this pull request as draft July 4, 2024 19:46
@J0 J0 marked this pull request as ready for review July 4, 2024 19:46
J0
J0 previously approved these changes Jul 4, 2024
View reviewed changes
@J0 J0 changed the base branch from main to dependabot/npm_and_yarn/ws-8.17.1 July 4, 2024 19:56
@J0 J0 changed the base branch from dependabot/npm_and_yarn/ws-8.17.1 to main July 4, 2024 19:56
@github-actions github-actions bot changed the title chore(main): release 0.4.1 chore(main): release 0.5.0 Jul 4, 2024
@J0 J0 force-pushed the release-please--branches--main branch from 34680eb to 1f64e81 Compare July 4, 2024 20:35
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 1f64e81 to 92b7b2c Compare July 4, 2024 20:35
@github-actions GitHub Actions
Copy link
Contributor Author

github-actions bot commented Jul 4, 2024

Release candidate v0.5.0-rc.4 published.

@J0
Copy link
Contributor

J0 commented Jul 4, 2024

Mistake there - the CI bump should have been a fix or a chore:

@J0 J0 dismissed their stale review July 4, 2024 20:40

need to figure out how to go back to v0.4.1

@RBarucco-jr RBarucco-jr mentioned this pull request Jul 27, 2024
Merged
@networkpsych networkpsych mentioned this pull request Jul 27, 2024
Open
@CropWatchDevelopment CropWatchDevelopment mentioned this pull request Jul 27, 2024
Open
@RBarucco-jr RBarucco-jr mentioned this pull request Jul 30, 2024
Merged
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 92b7b2c to 6dc5f03 Compare July 30, 2024 09:48
@github-actions GitHub Actions
Copy link
Contributor Author

Release candidate v0.5.0-rc.5 published.

@hf
Copy link
Collaborator

hf commented Jul 30, 2024

@J0 Maybe you could revert the PR, then re-add it with a fixed title. I think Release Please is smart enough to detect this?

@J0
Copy link
Contributor

J0 commented Jul 30, 2024

Sure let's try that now

@J0
Copy link
Contributor

J0 commented Jul 30, 2024

Opened one here - #44 is there a dedicated semantic prefix for reverts?

@J0 J0 marked this pull request as draft July 30, 2024 13:27
@J0 J0 marked this pull request as ready for review July 30, 2024 13:27
@J0 J0 force-pushed the release-please--branches--main branch from 6dc5f03 to 0e6adda Compare July 30, 2024 13:28
@RBarucco-jr RBarucco-jr mentioned this pull request Jul 31, 2024
Merged
@RBarucco-jr RBarucco-jr mentioned this pull request Aug 1, 2024
Merged
@CropWatchDevelopment CropWatchDevelopment mentioned this pull request Aug 1, 2024
Open
@RBarucco-jr RBarucco-jr mentioned this pull request Aug 2, 2024
Merged
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 0e6adda to 5095bf5 Compare August 19, 2024 10:43
@github-actions GitHub Actions
Copy link
Contributor Author

Release candidate v0.5.0-rc.7 published.

@github-actions github-actions bot force-pushed the release-please--branches--main branch from 5095bf5 to 4ba176a Compare August 19, 2024 10:52
@github-actions GitHub Actions
Copy link
Contributor Author

Release candidate v0.5.0-rc.8 published.

@hf hf merged commit 9cd6813 into main Aug 19, 2024
@hf hf deleted the release-please--branches--main branch August 19, 2024 11:16
@github-actions GitHub Actions
Copy link
Contributor Author

🤖 Created releases:

@aloisklink aloisklink mentioned this pull request Aug 19, 2024
Closed
2 tasks
@CropWatchDevelopment CropWatchDevelopment mentioned this pull request Sep 10, 2024
Open
@networkpsych networkpsych mentioned this pull request Sep 10, 2024
Open
@ShivajiVS ShivajiVS mentioned this pull request Sep 10, 2024
Open
@ShivajiVS ShivajiVS mentioned this pull request Sep 20, 2024
Merged
@mightysai1997 mightysai1997 mentioned this pull request Sep 22, 2024
Open
@josetutis josetutis mentioned this pull request Oct 26, 2024
Open
@BhruguR BhruguR mentioned this pull request Nov 2, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@hf hf hf approved these changes

@J0 J0 J0 left review comments

Assignees
No one assigned
Labels
autorelease: tagged
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@J0 @hf