Repository navigation
chore(tinycloud-node): release 1.26.6 - #605
Merged
Merged
Conversation
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.
Release 1.26.6: version + changelog only.
Content (fixed, on main at c92e768; v1.26.5 = 8802d3b):
/delegateand/revokesignatures checked before any lockChanges:
tinycloud-node-server/Cargo.toml,Cargo.lock,test/m1-realdata-e2e/Cargo.lock1.26.5 -> 1.26.6 (cargo metadata --lockedpasses for both lock files).CHANGELOG.mdmoves those entries from[Unreleased]to[1.26.6]and adds upgrade notes:m20261113_010000_artifact_chunks: what it changes, its 500 ms lock wait, and theseaql_migrationsstep needed before running 1.26.5 against the migrated schema (and restoring that row before returning to 1.26.6);statement_timeoutnow answer 503, and a warning is logged at startup if the removeddatabase.bulk_statement_timeout_msis still set;90841a34e6ea5b581374f50abe70e580496e6814bc83f61f20fd4c9e090e5d51(raw5419a6fbb73efe8b4430e4ab76d5e2970b2c9204525854e23f59dbdc01f4e250).The checkpoint-parts entry now says the switch is off by default, that capacities are checked when a database is written, and that any in-memory load over 8 MiB waits for a transfer slot. That last point replaces a DuckDB-export example that did not apply. All other
[Unreleased]lines are unchanged.Not merged, not tagged, no deploy, no image build dispatched.