Skip to content

document: a container swap records its preservation class - #3

Merged
unknovs merged 1 commit into
mainfrom
develop
Sep 4, 2026
Merged

document: a container swap records its preservation class#3
unknovs merged 1 commit into
mainfrom
develop

Conversation

@unknovs

@unknovs unknovs commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

No description provided.

… write; set_preservation_class dropped

replace_container_blob takes an optional preservation_class (none | b_lt | preservation), validated before any write and applied in the same UPDATE as the new bytes, so an archive-timestamped refresh records its upgrade to long-term preservation atomically with the swap. The separate owner-scoped setter, which any other party on the document's access list could not pass after the bytes had already been replaced, is dropped by V10. The new unit test unit.document_archive.sql now runs in this repository's gate. Deploy this image before or together with document-store v0.1.1 (CHANGELOG v0.1.1).

Signed-off-by: GatisB <l22exc@gmail.com>
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@unknovs
unknovs merged commit 16a14f5 into main Sep 4, 2026
9 checks passed
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