Repository navigation
Release 1.5.0 - #181
Merged
Merged
Release 1.5.0#181
Conversation
Bumps setup.py and adds the version history entry, folding in the three "unreleased" lines that asked to be merged into the next release's entry (the login throttle, the query-upload security fix, and the query result identity fix). 1.5.0 rather than a patch: 46 PRs, four security fixes, three schema migrations and a new comparison view is not a patch on 1.4.8. The entry leads with the four things that affect existing deployments, two of which need an operator decision - TRUSTED_PROXY_COUNT for anyone behind a reverse proxy, and the orphaned files in instance/temp/uploads left by the query-upload change. Test count measured on master rather than carried over: 962 passed, 6 skipped, for 968 collected against 239 at v1.4.8. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GwSfzAD1ZwEoWY3eWvbYvX
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.
Bumps
setup.pyto 1.5.0 and adds the version history entry.Draft on purpose — the version number and the tone of the entry are the maintainer's call, and tagging is a separate act. Nothing here publishes anything.
Why 1.5.0 and not 1.4.9
46 merged PRs, four security fixes, three schema migrations and a new function comparison view. #177 argued a patch bump understates that, and this agrees.
What the entry does
Folds in the three
unreleased:lines that each said "merge this line into the next release's entry" — the login throttle (#101), the query-upload security fix (#169) and the query result identity fix (#40). They are gone from the list and their content is in the 1.5.0 entry.It leads with the four changes that affect existing deployments, because two of them need an operator to do something:
login_attempt,query_upload, UTC user timestamps) — idempotent migrations, nothing existing altered, no action beyond restarting.TRUSTED_PROXY_COUNTfor anyone behind a reverse proxy. Without it the new login throttle keys on the proxy's address, so ten failed logins from anywhere refuse everyone's next login.instance/temp/uploads/is orphaned and pre-upgrade queries cannot be promoted to samples..smdareport with a malformed sha256 is now accepted rather than refused with 400.Checked rather than carried over
master:962 passed, 6 skipped→ 968 collected, against 239 at v1.4.8, so "adds 729 tests". Run withFLASK_DEBUG=0; themcritweb:1.4.8image sets it to 1, which makesapp.debugtrue and fails threeSESSION_COOKIE_SECURE/ route-policy tests that are not actually broken.innerHTMLsink from Security: a family name is rendered as HTML by the type-ahead #168 stays closed, and CI does not install Playwright — worth fixing separately.TRUSTED_PROXY_COUNT, both new tables and the UTC timestamp format were each confirmed present in the tree rather than taken from the PR descriptions.Interaction with #176
If #176 lands first, the version moves to
pyproject.tomland this bump belongs there instead — this PR would then need rebasing onto that. #176 also has open questions on itsrequires-pythonfloor and CI matrix (commented there).🤖 Generated with Claude Code
https://claude.ai/code/session_01GwSfzAD1ZwEoWY3eWvbYvX