Repository navigation
chore(release): prepare 2.1.0 - #55
Merged
Merged
Conversation
Bump the backend version to 2.1.0 and add bilingual release notes for the deletion-safety, persistence and retention changes merged in PR #53 (issues #42-#52). SQLite schema moves 6 -> 8; rollback restores the verified schema-6 backup with image 2.0.4. Refs #54 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepare CleanArr 2.1.0 from
mainat5d808a2(PR #53, issues #42–#52).Closes #54.
Changes
backend/pyproject.tomlandbackend/src/cleanarr/api/app.py: version 2.0.4 → 2.1.0.docs/releases/v2.1.0.md: bilingual RU/EN release notes in the structure required bydocs/RELEASING.md.The version is a minor bump because SQLite moves from schema 6 to schema 8 (migration 7: retained-torrent record, migration 8: job error codes). Version 2.0.4 cannot open a schema-8 database. The release also adds the Downloads retention marker and new fail-closed safety reasons. Configuration schema 4 is unchanged. The latest-stable rehearsal (
v2.0.4 → candidate → restored v2.0.4) is already part ofcompatibility/rehearse_upgrade.pyfrom PR #53.Local validation on this commit
localStoragebreaks jsdom setup, so this run usedNODE_OPTIONS=--no-experimental-webstorage. CI uses Node 24.Release gates
compatibility.ymlon this branch: pinned real-service profile plus six upgrade/backup-rollback rehearsals.v2.1.0→docker-release.ymlre-runs both gates from a clean checkout and publishes the GHCR image, DEB/RPM, SBOMs,SHA256SUMSand attestations.Rollback
Stop CleanArr, keep the schema-8 database under a separate name, restore the verified schema-6 backup and pin image 2.0.4. The published tag will not be moved or recreated; artifact recovery follows
docs/RELEASING.md.🤖 Generated with Claude Code