Skip to content

Documentation: Educate about publishing pre-release packages#789

Closed
amotl wants to merge 1 commit intomainfrom
docs-prerelease
Closed

Documentation: Educate about publishing pre-release packages#789
amotl wants to merge 1 commit intomainfrom
docs-prerelease

Conversation

@amotl
Copy link
Member

@amotl amotl commented Mar 4, 2026

About

Improve developer documentation about how to publish pre-release packages.

References

@amotl amotl requested a review from mfussenegger March 4, 2026 09:17
Copy link
Member

@mfussenegger mfussenegger left a comment

Choose a reason for hiding this comment

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

Why bother with pre-releases if downstream projects could install from https+git instead?

I'd understand the point to highlight that it's now ready to testing/close to a release, but it's not like crate-python should have much changes anymore. The DB API is stable.

@amotl
Copy link
Member Author

amotl commented Mar 4, 2026

In this case, it also was about validating the packaging, which had flaws. However, I see that we don't necessarily need to document it.

@amotl amotl closed this Mar 4, 2026
@amotl amotl deleted the docs-prerelease branch March 4, 2026 10:03
@mfussenegger
Copy link
Member

, it also was about validating the packaging, which had flaws

If I'm not mistaken the flaws were in the github action workflow - the manual steps listed here would've bypassed that, no?
To catch such issues one would have to tag the release normally - except using a dev/rc suffix in the tag name.

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.

2 participants