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

chore(main): Release 30.10.0 #3106

Merged
merged 1 commit into from Mar 22, 2024

Conversation

daschbot
Copy link
Collaborator

@daschbot daschbot commented Mar 8, 2024

🤖 I have created a release beep boop

30.10.0 (2024-03-22)

Maintenance

Documentation

Enhancements

  • Add additional project export route that awaits the process (#3136) (70e0172)

Bug Fixes


This PR was generated with Release Please. See documentation.

@daschbot daschbot force-pushed the release-please--branches--main--components--dsp-api branch 3 times, most recently from 63486e0 to caeee16 Compare March 11, 2024 14:52
@mpro7
Copy link
Collaborator

mpro7 commented Mar 12, 2024

@siers please leave these release PRs unapproved, just to be on the safe side ;)

@BalduinLandolt BalduinLandolt removed their request for review March 12, 2024 08:52
@daschbot daschbot force-pushed the release-please--branches--main--components--dsp-api branch 4 times, most recently from f71f63e to f3136c9 Compare March 12, 2024 13:49
@seakayone
Copy link
Collaborator

@siers please leave these release PRs unapproved, just to be on the safe side ;)

I have approved it also. The reason being is that this way my review requested overview is not cluttered with this PR. I do not want to parse this every time I look at the overview. IMHO we should emphasize on this workflow and deem the danger of accidentially merging this PR as not as important.

@BalduinLandolt
Copy link
Collaborator

@siers please leave these release PRs unapproved, just to be on the safe side ;)

I have approved it also. The reason being is that this way my review requested overview is not cluttered with this PR. I do not want to parse this every time I look at the overview. IMHO we should emphasize on this workflow and deem the danger of accidentially merging this PR as not as important.

I simply un-requested the review from me :)
Also, this won't happen in the future, as new ones will be created as draft

@daschbot daschbot force-pushed the release-please--branches--main--components--dsp-api branch 12 times, most recently from e753e13 to a0ec74b Compare March 18, 2024 15:44
@daschbot daschbot force-pushed the release-please--branches--main--components--dsp-api branch 6 times, most recently from a3afe95 to 94eda4d Compare March 20, 2024 11:29
@daschbot daschbot changed the title chore(main): Release 30.9.1 chore(main): Release 30.10.0 Mar 20, 2024
@daschbot daschbot force-pushed the release-please--branches--main--components--dsp-api branch 4 times, most recently from 3a358cf to 2d83e9d Compare March 21, 2024 19:25
@daschbot daschbot force-pushed the release-please--branches--main--components--dsp-api branch from 2d83e9d to 30a28d5 Compare March 22, 2024 07:15
@mpro7 mpro7 merged commit b1d5743 into main Mar 22, 2024
9 checks passed
@mpro7 mpro7 deleted the release-please--branches--main--components--dsp-api branch March 22, 2024 07:33
@daschbot
Copy link
Collaborator Author

🤖 Release is at https://github.com/dasch-swiss/dsp-api/releases/tag/v30.10.0 🌻

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

Successfully merging this pull request may close these issues.

None yet

5 participants