Repository navigation
chore(release): prepare for 2026.3.3 - #2076
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…orkflow The 2026.3.3 release hit three problems in the changelog-to-jira script: - New-JiraIssue has no -Assignee parameter in JiraPS 2.16, so creating a ticket with an assignee failed. The assignee is now sent through -Fields as an accountId. - The hardcoded DGW transition IDs no longer exist, so tickets stayed in Backlog. Transitions are now picked by the status they lead to, taking the furthest one along Backlog > To Do > Development > Reviewing > Done. When none moves forward, the error lists what Jira offers. - The README asked for a scoped API token, which Jira rejects on the site URL the script calls. It now asks for a plain token. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
Implementation notes:
|
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The version metadata is consistent, the changelog matches the included changes, and the JiraPS usage aligns with its supported API.
0 open findings
What changed in this PR
Prepares the 2026.3.3 hotfix release and improves the changelog-to-Jira workflow.
Changes:
- Bumps product and package versions to 2026.3.3.
- Adds release and packaging changelog entries.
- Makes Jira assignment and workflow transitions more robust.
| File | Description |
|---|---|
VERSION |
Updates the release version. |
Cargo.toml |
Updates the Rust workspace version. |
Cargo.lock |
Refreshes workspace package versions. |
fuzz/Cargo.lock |
Refreshes the fuzz package version. |
DevolutionsGateway.psd1 |
Updates the PowerShell module version. |
DesktopAgent.csproj |
Updates the Desktop Agent version. |
AppxManifest.xml |
Updates the shell extension version. |
CHANGELOG.md |
Documents the hotfix release. |
package/Linux/CHANGELOG.md |
Adds the Gateway package release. |
package/AgentLinux/CHANGELOG.md |
Adds the Agent package release. |
changelog-to-jira/SKILL.md |
Documents transition-failure handling. |
changelog-to-jira/README.md |
Corrects API-token guidance. |
invoke-jira.ps1 |
Resolves assignees and transitions dynamically. |
No material findings identified.
🧠 Review effort: Balanced
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
2026.3.3 (2026-10-14)
Features
dgw: keep agent tunnel data in a shared gateway.db (#2039) (e8ac5ef235) (DGW-464)
Agent Tunnel data moves from
agent_tunnel.dbtogateway.dbin the Gateway data directory.Gateway creates
gateway.dbon every start, even when Agent Tunnel is disabled.On the first start after upgrading, Gateway imports and removes an existing
agent_tunnel.db, so enrolled agents keep working without enrolling again.Downgrading afterwards means agents have to enroll again, because earlier versions only read
agent_tunnel.db.dgw: honor an explicit agent on KDC tokens (#2068) (458a0db6e4) (DGW-453)
KDC tokens can name an explicit agent with
jet_agent_id, as association and JMUX tokens already do./jet/KdcProxythen sends every Kerberos message through that agent or fails, without falling back to a direct connection or another agent; tokens without the claim keep working as before.Previously, the client's Kerberos traffic for an RDP session pinned to an agent could reach the KDC directly from Gateway or through a different agent.
Through an agent, the KDC must use
tcp://: audp://KDC with an explicit agent is rejected.Bug Fixes
dgw,agent: fix Windows service crash at startup (#2069) (20c0119493) (DGW-460)
The Gateway Windows service could crash at startup with an access violation in
ntdll.dlland never start, as seen after updating to 2026.3.2 on Windows Server 2016.The Agent Windows service could crash the same way and is fixed too.
When the service fails to start, for example because of an invalid configuration, Gateway and Agent now exit with a nonzero status, so service managers such as systemd can detect the failure and restart them.