Repository navigation
Prepare v3.1.0 and record missing release milestones - #339
Merged
Merged
Conversation
Set VERSION to 3.1.0 and add candidate release notes for the work merged since v3.0.0: SOCKS5 proxy routes, automation through jump hosts, browser login management, workspace presets, script-policy and restore hardening. The notes state that 3.0.0 must not be started on data used by 3.1, since it ignores SOCKS5 routes and would connect routed hosts directly. Record the v3.1.0 candidate in the release manifest and roadmap, and the milestones created for v2.7.0, v3.0.0 and v3.1.0.
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Prepares WebSSH 3.1.0 from
mainat b7b1ff5 and records the release milestones that were missing since v2.7.0.Version
The work merged since v3.0.0 adds functionality and configuration (SOCKS5 proxy routes with
SOCKS_REMOTE_DNS_ALLOWLIST/SOCKS_PROXY_MAX_RECORDS, automation through jump hosts, browser login management, workspace presets, support reports), so this is a minor release rather than 3.0.1. The3.0image tag stays on 3.0.0;3.1andlatestfollow 3.1.0.Changes
app/version.py:VERSION = '3.1.0'.docs/releases/v3.1.0.md: candidate notes, configuration, upgrade/rollback precautions and image tags. Validation stays pending until the tag is verified.docs/release-history.json: v3.1.0 candidate (17 PRs, Display the WebSSH version number #327 by Show the WebSSH version and update the Python base image to 3.14.10 #328, Feature Request: Support SOCKS5 Proxy for Individual SSH Connections #334 by Add per-host SOCKS5 proxy routes #336), milestone numbers for v2.7.0/v3.0.0 and a datednative_milestone_followupsentry. Historical snapshots are unchanged.ROADMAP.md,docs/project-planning.md: preparation status and the 2026-11-14 milestone update.docs/wiki/Upgrading-Rollback-and-FAQ.md: v3.1.0 compatibility section.Rollback finding
3.0.0 accepts profiles with
socks_proxy_idand ignores the field. Starting 3.0.0 on data used by 3.1 would connect SOCKS-routed hosts directly. The notes and upgrade guide require rollback by restoring the pre-upgrade volumes.Milestones
Membership follows first tagged inclusion (checked with
git merge-base --is-ancestoragainst each tag). Superseded Dependabot PRs #322/#323 are not assigned. No due dates were set.Validation
tests/test_version.py, documentation surface, public product surface, branding, repository hygiene, license consistency and CI change scope: 201 passed, 1 skipped.scripts/check_repository_hygiene.pyandscripts/check_license_consistency.pypass.Refs #338. Merging does not publish a release; tag and image verification follow in #338.