Skip to content

Release 0.1.0 - #171

Merged
tamnd merged 1 commit into
mainfrom
release-0.1.0
Oct 8, 2026
Merged

tamnd merged 1 commit into
mainfrom
release-0.1.0

Conversation

@tamnd

@tamnd tamnd commented Oct 8, 2026

Copy link
Copy Markdown
Owner

Summary

Release 0.1.0, the release that closes M1 (#2). The version moves from 0.0.18 to 0.1.0 in each crate and in the lock files, and the changes since 0.0.18 move from Unreleased to the 0.1.0 section of the changelog. No crate is published.

Changes since 0.0.18: set_config (#163), the transaction mode checks after a query (#163), the has_*_privilege functions and pg_has_role with the privileges of the static catalog rows (#165), the catalog of user objects (#166), the stored form of an analyzed expression (#167), cargo xtask lifts (#168), cargo xtask bench (#169) and the repair of the doc comments (#170). The catalog of user objects and the stored form have no part that a user can see yet, so the changelog does not list them.

Test plan

  • The full test suite, the generated file checks and cargo doc with -D warnings pass on server1 at this commit.
  • After the merge, the tag v0.1.0 gets the reproducible build check of the nightly workflow: two release builds of rupg in two directories must give the same SHA-256.

@tamnd tamnd added this to the M1: The file milestone Oct 8, 2026
@tamnd tamnd added kind/milestone A milestone from spec/23-milestones.md. area/build The workspace, CI, release and the layer rule. labels Oct 8, 2026
@tamnd tamnd self-assigned this Oct 8, 2026
@tamnd
tamnd merged commit 573a5a4 into main Oct 8, 2026
5 checks passed
@tamnd
tamnd deleted the release-0.1.0 branch October 8, 2026 07:14
@tamnd tamnd mentioned this pull request Oct 8, 2026
16 of 18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/build The workspace, CI, release and the layer rule. kind/milestone A milestone from spec/23-milestones.md.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant