Skip to content

Conversation

@lcian
Copy link
Member

@lcian lcian commented Oct 30, 2025

Sets up the necessary things for publishing both the rust and python clients.

@lcian lcian marked this pull request as ready for review October 30, 2025 15:30
@lcian lcian requested a review from a team as a code owner October 30, 2025 15:30
Base automatically changed from lcian/feat/move-clients to main October 30, 2025 17:38
@@ -0,0 +1,19 @@
changelogPolicy: auto

targets:
Copy link
Member

Choose a reason for hiding this comment

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

Let's please double-check if we also need to upload tosentry-sdk-assets.

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 have no idea what that does.
An org-wide search for this bucket name is not very helpful: https://github.com/search?q=org%3Agetsentry%20sentry-sdk-assets&type=code
Any pointers?

@lcian lcian added bug Something isn't working and removed bug Something isn't working labels Oct 31, 2025
@lcian lcian added the documentation Improvements or additions to documentation label Oct 31, 2025
@lcian lcian removed the documentation Improvements or additions to documentation label Oct 31, 2025
@lcian
Copy link
Member Author

lcian commented Oct 31, 2025

Tested this and it works, see getsentry/publish#6550
(the cargo doc step failed just because the branch is behind main)

Also I think we'll want these releases to be auto-approved.
Created a PR for that here: getsentry/publish#6551

@lcian lcian merged commit a31a374 into main Oct 31, 2025
16 checks passed
@lcian lcian deleted the lcian/feat/client-release-setup-clean branch October 31, 2025 13:17
jan-auer added a commit that referenced this pull request Oct 31, 2025
* main:
  meta(client): Release setup (#157)
  feat(server): Improve error handling during shutdown (#161)
  feat: Allow defining a per-usecase/client default expiration policy (#158)
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