Skip to content

Develop v2.1.0 #1941

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ivis-miyachi merged 2 commits into from
Oct 9, 2026
Merged

Develop v2.1.0 #1941

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9f04d5b
fix down_revision(WEKO3_OPE-10145)
ivis-miyachi Oct 9, 2026
1f33cbd
Merge pull request #1940 from RCOSDP/fix/OPE10145
ivis-miyachi Oct 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...venio-files-rest/invenio_files_rest/alembic/faf4faa08601_add_column_file_readonly_keys.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@

# revision identifiers, used by Alembic.
revision = 'faf4faa08601'
down_revision = '8644b32a3eec'
down_revision = '8ae99b034410'

@sourcery-ai sourcery-ai Bot Oct 9, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟠 High · Location upgrades and queries fail

When a fresh database is upgraded, or an existing database is at 8644b32a3eec, faf4faa08601 skips 8644b32a3eec, so Alembic cannot plan upgrades from that revision, and fresh schemas miss the S3 columns. Existing rows also miss the read-only-key columns; location access then fails with a database error.

Restore 8644b32a3eec as down_revision so Alembic follows the migration chain and applies the required column migrations.

Prompt for AI agents 
In `modules/invenio-files-rest/invenio_files_rest/alembic/faf4faa08601_add_column_file_readonly_keys.py` at line 16:

**Location upgrades and queries fail**

When a fresh database is upgraded, or an existing database is at `8644b32a3eec`, `faf4faa08601` skips `8644b32a3eec`, so Alembic cannot plan upgrades from that revision, and fresh schemas miss the S3 columns. Existing rows also miss the read-only-key columns; location access then fails with a database error.

Restore `8644b32a3eec` as `down_revision` so Alembic follows the migration chain and applies the required column migrations.

branch_labels = ()
depends_on = None

Expand Down
Loading