Publish release assets from manually dispatched devpc release runs - #59

Merged
logancsack merged 4 commits into
mainfrom
fix/devpc-release-dispatch-publish
Aug 9, 2026
Merged

Publish release assets from manually dispatched devpc release runs#59
logancsack merged 4 commits into
mainfrom
fix/devpc-release-dispatch-publish

Conversation

@logancsack

@logancsacklogancsack commented Aug 9, 2026•
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Owner

A workflow_dispatch run of devpc-managed-release.yml built and verified the artifact but published nothing — the release step was gated on tag refs only, so the dispatch path could not produce the checksummed GitHub release that the workspace pin (config/t3code-release.json in remote-dev) consumes.

Dispatch runs now publish too: the devpc-v tag is derived from the version input (0.0.28-devpc.54 → devpc-v0.0.28.54) and gh release create --target "$GITHUB_SHA" creates the tag at the built commit. Tag-push runs are unchanged.

Motivation right now: devpc-v0.0.28.54 needs to be cut from main (8818409, PR #58) and the environment driving this release can push branches but not tags, so the dispatch path is the release mechanism.

Generated by Claude Code

Summary by CodeRabbit

  • Chores
    • Release workflows can now be started manually with a specified version.
    • Releases triggered by tags or manual runs are created from the appropriate commit.
    • Published packages and checksums now include automatically generated release notes.

@claude
Publish release assets from manually dispatched devpc release runs
14d02b3
A workflow_dispatch run built and verified the artifact but published
nothing, leaving the dispatch path unable to produce the checksummed
release the workspace pin consumes. Dispatch runs now create the release
too, deriving the devpc-v tag from the version input and letting gh create
the tag at the built commit.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@github-actionsgithub-actionsBot added size:S vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. labels Aug 9, 2026
@coderabbitai

coderabbitaiBot commented Aug 9, 2026•
edited
Loading

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@logancsack, you've reached your PR review limit, so we couldn't start this review.

Next review available in:51 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 2b1befb5-6280-4efb-9eea-7e0e4826f6d5

📥 Commits

Reviewing files that changed from the base of the PR and between 14d02b3 and 4e96e9e.

📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
📝 Walkthrough

Walkthrough

The release workflow now supports tag pushes and manual dispatches. Manual dispatches convert the supplied version into a devpc-v... tag at GITHUB_SHA. Tag pushes use GITHUB_REF_NAME. Both paths upload release artifacts with generated notes.

Changes

DevPC release publishing

Layer / File(s)Summary
Release trigger and publishing flow
.github/workflows/devpc-managed-release.yml		Manual runs create a release tag from the version input at GITHUB_SHA. Tag-triggered runs retain GITHUB_REF_NAME. Both paths upload the package and checksum with generated release notes.

Estimated code review effort: 2 (Simple) | ~10 minutes

Poem

A rabbit checks the release gate,
Tags hop out and versions wait.
The package and checksum join the run,
Notes bloom softly in the sun.
GITHUB_SHA marks where releases grow.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly describes the main change: publishing release assets from manually dispatched DevPC release runs.
Description check✅ PassedThe description explains what changed and why, including dispatch behavior and release tag creation; the optional checklist is omitted.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/devpc-release-dispatch-publish

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot reviewed Aug 9, 2026
View reviewed changes

@chatgpt-codex-connectorchatgpt-codex-connectorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:14d02b3d00

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread.github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml Outdated
@claude
Validate dispatch version and guard existing-tag mismatches
ad596f7
A dispatch run now rejects a version input that does not match the
N.N.N-devpc.N shape, and resolves any pre-existing release tag before
publishing: gh release create's --target only applies when the tag is
absent, so an existing tag at another commit would have silently
labeled this run's assets with the wrong source. Refuse instead.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
coderabbitai[bot]
coderabbitaiBot suggested changes Aug 9, 2026
View reviewed changes

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/devpc-managed-release.yml:
- Line 160: Update the release-tag logic near the version input handling to
validate the base version against the versions in both apps/server/package.json
and apps/web/package.json before publishing. Derive the tag from the checked-out
package metadata, or fail when the supplied input’s base version does not match
both packages, so a mismatched artifact cannot be published under an incorrect
devpc tag.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: d64e421a-3d9c-4b1d-adad-f74cd391e7aa

📥 Commits

Reviewing files that changed from the base of the PR and between 8818409 and 14d02b3.

📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml

Comment thread.github/workflows/devpc-managed-release.yml Outdated
chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot reviewed Aug 9, 2026
View reviewed changes

@chatgpt-codex-connectorchatgpt-codex-connectorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:ad596f7796

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread.github/workflows/devpc-managed-release.yml Outdated
Comment thread.github/workflows/devpc-managed-release.yml Outdated
@claude
Pass the dispatch version via env and cross-check package versions
895f314
The version input now reaches the publish script through the job
environment instead of template expansion, so it cannot expand into
shell syntax. Its base version is also compared against the versions
in apps/server and apps/web package.json, refusing to label an
artifact with a version the packages do not carry.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@claude
Fail the publish when the existing-tag lookup itself errors
4e96e9e
The tag-mismatch guard resolved the tag with gh api and swallowed
every failure as absence, so a transient lookup error could still
publish under a stale tag. git ls-remote distinguishes the two:
empty output means the tag is absent, a nonzero exit fails the step.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@logancsack
logancsack merged commit 872106e into mainAug 9, 2026
12 checks passed
@logancsacklogancsack mentioned this pull request Aug 9, 2026
Merged
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@chatgpt-codex-connectorchatgpt-codex-connector[bot]chatgpt-codex-connector[bot] left review comments
+1 more reviewer
@coderabbitaicoderabbitai[bot]coderabbitai[bot] approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@logancsack@claude
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
Publish release assets from manually dispatched devpc release runs - #59
Merged
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Aug 9, 2026
Merged
Publish release assets from manually dispatched devpc release runs#59
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Conversation
@logancsack
@logancsacklogancsack
commented
Aug 9, 2026•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Owner
A workflow_dispatch run of devpc-managed-release.yml built and verified the artifact but published nothing — the release step was gated on tag refs only, so the dispatch path could not produce the checksummed GitHub release that the workspace pin (config/t3code-release.json in remote-dev) consumes.
Dispatch runs now publish too: the devpc-v tag is derived from the version input (0.0.28-devpc.54 → devpc-v0.0.28.54) and gh release create --target "$GITHUB_SHA" creates the tag at the built commit. Tag-push runs are unchanged.
Motivation right now: devpc-v0.0.28.54 needs to be cut from main (8818409, PR #58) and the environment driving this release can push branches but not tags, so the dispatch path is the release mechanism.
Generated by Claude Code
Summary by CodeRabbit
  • Chores
    • Release workflows can now be started manually with a specified version.
    • Releases triggered by tags or manual runs are created from the appropriate commit.
    • Published packages and checksums now include automatically generated release notes.
@claude
Publish release assets from manually dispatched devpc release runs
14d02b3
A workflow_dispatch run built and verified the artifact but published
nothing, leaving the dispatch path unable to produce the checksummed
release the workspace pin consumes. Dispatch runs now create the release
too, deriving the devpc-v tag from the version input and letting gh create
the tag at the built commit.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@github-actionsgithub-actionsBot
added

size:S

vouch:trusted
PR author is trusted by repo permissions or the VOUCHED list.
labels
Aug 9, 2026
@coderabbitai
coderabbitaiBot
commented
Aug 9, 2026•

edited

Loading

Copy link


Copy Markdown

Review Change Stack
Warning
Review limit reached
@logancsack, you've reached your PR review limit, so we couldn't start this review.
Next review available in:51 minutes
You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.
How can I continue?
After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.
To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.
How do review limits work?
CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.
For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.
Please refer docs for additional details.
Review details
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 2b1befb5-6280-4efb-9eea-7e0e4826f6d5
📥 Commits
Reviewing files that changed from the base of the PR and between 14d02b3 and 4e96e9e.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
📝 Walkthrough
Walkthrough
The release workflow now supports tag pushes and manual dispatches. Manual dispatches convert the supplied version into a devpc-v... tag at GITHUB_SHA. Tag pushes use GITHUB_REF_NAME. Both paths upload release artifacts with generated notes.
Changes
DevPC release publishing
Layer / File(s)Summary
Release trigger and publishing flow
.github/workflows/devpc-managed-release.yml		Manual runs create a release tag from the version input at GITHUB_SHA. Tag-triggered runs retain GITHUB_REF_NAME. Both paths upload the package and checksum with generated release notes.
Estimated code review effort: 2 (Simple) | ~10 minutes
Poem
A rabbit checks the release gate,

Tags hop out and versions wait.

The package and checksum join the run,

Notes bloom softly in the sun.
GITHUB_SHA marks where releases grow.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly describes the main change: publishing release assets from manually dispatched DevPC release runs.
Description check✅ PassedThe description explains what changed and why, including dispatch behavior and release tag creation; the optional checklist is omitted.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/devpc-release-dispatch-publish
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:14d02b3d00
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Validate dispatch version and guard existing-tag mismatches
ad596f7
A dispatch run now rejects a version input that does not match the
N.N.N-devpc.N shape, and resolves any pre-existing release tag before
publishing: gh release create's --target only applies when the tag is
absent, so an existing tag at another commit would have silently
labeled this run's assets with the wrong source. Refuse instead.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
coderabbitai[bot]
coderabbitaiBot
suggested changes
Aug 9, 2026
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/devpc-managed-release.yml:
- Line 160: Update the release-tag logic near the version input handling to
validate the base version against the versions in both apps/server/package.json
and apps/web/package.json before publishing. Derive the tag from the checked-out
package metadata, or fail when the supplied input’s base version does not match
both packages, so a mismatched artifact cannot be published under an incorrect
devpc tag.

🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
  •  Push a commit to this branch (recommended)
  •  Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: d64e421a-3d9c-4b1d-adad-f74cd391e7aa
📥 Commits
Reviewing files that changed from the base of the PR and between 8818409 and 14d02b3.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:ad596f7796
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Pass the dispatch version via env and cross-check package versions
895f314
The version input now reaches the publish script through the job
environment instead of template expansion, so it cannot expand into
shell syntax. Its base version is also compared against the versions
in apps/server and apps/web package.json, refusing to label an
artifact with a version the packages do not carry.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@claude
Fail the publish when the existing-tag lookup itself errors
4e96e9e
The tag-mismatch guard resolved the tag with gh api and swallowed
every failure as absence, so a transient lookup error could still
publish under a stale tag. git ls-remote distinguishes the two:
empty output means the tag is absent, a nonzero exit fails the step.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@logancsack
logancsack
merged commit 872106e
into
mainAug 9, 2026

12 checks passed

@logancsacklogancsack
mentioned this pull request
Aug 9, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@chatgpt-codex-connectorchatgpt-codex-connector[bot]chatgpt-codex-connector[bot] left review comments

+1 more reviewer

@coderabbitaicoderabbitai[bot]coderabbitai[bot] approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@logancsack@claude

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Publish release assets from manually dispatched devpc release runs - #59
Merged
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Aug 9, 2026
Merged
Publish release assets from manually dispatched devpc release runs#59
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Conversation
@logancsack
@logancsacklogancsack
commented
Aug 9, 2026•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Owner
A workflow_dispatch run of devpc-managed-release.yml built and verified the artifact but published nothing — the release step was gated on tag refs only, so the dispatch path could not produce the checksummed GitHub release that the workspace pin (config/t3code-release.json in remote-dev) consumes.
Dispatch runs now publish too: the devpc-v tag is derived from the version input (0.0.28-devpc.54 → devpc-v0.0.28.54) and gh release create --target "$GITHUB_SHA" creates the tag at the built commit. Tag-push runs are unchanged.
Motivation right now: devpc-v0.0.28.54 needs to be cut from main (8818409, PR #58) and the environment driving this release can push branches but not tags, so the dispatch path is the release mechanism.
Generated by Claude Code
Summary by CodeRabbit
  • Chores
    • Release workflows can now be started manually with a specified version.
    • Releases triggered by tags or manual runs are created from the appropriate commit.
    • Published packages and checksums now include automatically generated release notes.
@claude
Publish release assets from manually dispatched devpc release runs
14d02b3
A workflow_dispatch run built and verified the artifact but published
nothing, leaving the dispatch path unable to produce the checksummed
release the workspace pin consumes. Dispatch runs now create the release
too, deriving the devpc-v tag from the version input and letting gh create
the tag at the built commit.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@github-actionsgithub-actionsBot
added

size:S

vouch:trusted
PR author is trusted by repo permissions or the VOUCHED list.
labels
Aug 9, 2026
@coderabbitai
coderabbitaiBot
commented
Aug 9, 2026•

edited

Loading

Copy link


Copy Markdown

Review Change Stack
Warning
Review limit reached
@logancsack, you've reached your PR review limit, so we couldn't start this review.
Next review available in:51 minutes
You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.
How can I continue?
After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.
To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.
How do review limits work?
CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.
For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.
Please refer docs for additional details.
Review details
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 2b1befb5-6280-4efb-9eea-7e0e4826f6d5
📥 Commits
Reviewing files that changed from the base of the PR and between 14d02b3 and 4e96e9e.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
📝 Walkthrough
Walkthrough
The release workflow now supports tag pushes and manual dispatches. Manual dispatches convert the supplied version into a devpc-v... tag at GITHUB_SHA. Tag pushes use GITHUB_REF_NAME. Both paths upload release artifacts with generated notes.
Changes
DevPC release publishing
Layer / File(s)Summary
Release trigger and publishing flow
.github/workflows/devpc-managed-release.yml		Manual runs create a release tag from the version input at GITHUB_SHA. Tag-triggered runs retain GITHUB_REF_NAME. Both paths upload the package and checksum with generated release notes.
Estimated code review effort: 2 (Simple) | ~10 minutes
Poem
A rabbit checks the release gate,

Tags hop out and versions wait.

The package and checksum join the run,

Notes bloom softly in the sun.
GITHUB_SHA marks where releases grow.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly describes the main change: publishing release assets from manually dispatched DevPC release runs.
Description check✅ PassedThe description explains what changed and why, including dispatch behavior and release tag creation; the optional checklist is omitted.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/devpc-release-dispatch-publish
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:14d02b3d00
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Validate dispatch version and guard existing-tag mismatches
ad596f7
A dispatch run now rejects a version input that does not match the
N.N.N-devpc.N shape, and resolves any pre-existing release tag before
publishing: gh release create's --target only applies when the tag is
absent, so an existing tag at another commit would have silently
labeled this run's assets with the wrong source. Refuse instead.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
coderabbitai[bot]
coderabbitaiBot
suggested changes
Aug 9, 2026
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/devpc-managed-release.yml:
- Line 160: Update the release-tag logic near the version input handling to
validate the base version against the versions in both apps/server/package.json
and apps/web/package.json before publishing. Derive the tag from the checked-out
package metadata, or fail when the supplied input’s base version does not match
both packages, so a mismatched artifact cannot be published under an incorrect
devpc tag.

🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
  •  Push a commit to this branch (recommended)
  •  Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: d64e421a-3d9c-4b1d-adad-f74cd391e7aa
📥 Commits
Reviewing files that changed from the base of the PR and between 8818409 and 14d02b3.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:ad596f7796
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Pass the dispatch version via env and cross-check package versions
895f314
The version input now reaches the publish script through the job
environment instead of template expansion, so it cannot expand into
shell syntax. Its base version is also compared against the versions
in apps/server and apps/web package.json, refusing to label an
artifact with a version the packages do not carry.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@claude
Fail the publish when the existing-tag lookup itself errors
4e96e9e
The tag-mismatch guard resolved the tag with gh api and swallowed
every failure as absence, so a transient lookup error could still
publish under a stale tag. git ls-remote distinguishes the two:
empty output means the tag is absent, a nonzero exit fails the step.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@logancsack
logancsack
merged commit 872106e
into
mainAug 9, 2026

12 checks passed

@logancsacklogancsack
mentioned this pull request
Aug 9, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@chatgpt-codex-connectorchatgpt-codex-connector[bot]chatgpt-codex-connector[bot] left review comments

+1 more reviewer

@coderabbitaicoderabbitai[bot]coderabbitai[bot] approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@logancsack@claude

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Publish release assets from manually dispatched devpc release runs - #59
Merged
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Aug 9, 2026
Merged
Publish release assets from manually dispatched devpc release runs#59
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Conversation
@logancsack
@logancsacklogancsack
commented
Aug 9, 2026•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Owner
A workflow_dispatch run of devpc-managed-release.yml built and verified the artifact but published nothing — the release step was gated on tag refs only, so the dispatch path could not produce the checksummed GitHub release that the workspace pin (config/t3code-release.json in remote-dev) consumes.
Dispatch runs now publish too: the devpc-v tag is derived from the version input (0.0.28-devpc.54 → devpc-v0.0.28.54) and gh release create --target "$GITHUB_SHA" creates the tag at the built commit. Tag-push runs are unchanged.
Motivation right now: devpc-v0.0.28.54 needs to be cut from main (8818409, PR #58) and the environment driving this release can push branches but not tags, so the dispatch path is the release mechanism.
Generated by Claude Code
Summary by CodeRabbit
  • Chores
    • Release workflows can now be started manually with a specified version.
    • Releases triggered by tags or manual runs are created from the appropriate commit.
    • Published packages and checksums now include automatically generated release notes.
@claude
Publish release assets from manually dispatched devpc release runs
14d02b3
A workflow_dispatch run built and verified the artifact but published
nothing, leaving the dispatch path unable to produce the checksummed
release the workspace pin consumes. Dispatch runs now create the release
too, deriving the devpc-v tag from the version input and letting gh create
the tag at the built commit.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@github-actionsgithub-actionsBot
added

size:S

vouch:trusted
PR author is trusted by repo permissions or the VOUCHED list.
labels
Aug 9, 2026
@coderabbitai
coderabbitaiBot
commented
Aug 9, 2026•

edited

Loading

Copy link


Copy Markdown

Review Change Stack
Warning
Review limit reached
@logancsack, you've reached your PR review limit, so we couldn't start this review.
Next review available in:51 minutes
You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.
How can I continue?
After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.
To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.
How do review limits work?
CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.
For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.
Please refer docs for additional details.
Review details
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 2b1befb5-6280-4efb-9eea-7e0e4826f6d5
📥 Commits
Reviewing files that changed from the base of the PR and between 14d02b3 and 4e96e9e.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
📝 Walkthrough
Walkthrough
The release workflow now supports tag pushes and manual dispatches. Manual dispatches convert the supplied version into a devpc-v... tag at GITHUB_SHA. Tag pushes use GITHUB_REF_NAME. Both paths upload release artifacts with generated notes.
Changes
DevPC release publishing
Layer / File(s)Summary
Release trigger and publishing flow
.github/workflows/devpc-managed-release.yml		Manual runs create a release tag from the version input at GITHUB_SHA. Tag-triggered runs retain GITHUB_REF_NAME. Both paths upload the package and checksum with generated release notes.
Estimated code review effort: 2 (Simple) | ~10 minutes
Poem
A rabbit checks the release gate,

Tags hop out and versions wait.

The package and checksum join the run,

Notes bloom softly in the sun.
GITHUB_SHA marks where releases grow.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly describes the main change: publishing release assets from manually dispatched DevPC release runs.
Description check✅ PassedThe description explains what changed and why, including dispatch behavior and release tag creation; the optional checklist is omitted.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/devpc-release-dispatch-publish
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:14d02b3d00
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Validate dispatch version and guard existing-tag mismatches
ad596f7
A dispatch run now rejects a version input that does not match the
N.N.N-devpc.N shape, and resolves any pre-existing release tag before
publishing: gh release create's --target only applies when the tag is
absent, so an existing tag at another commit would have silently
labeled this run's assets with the wrong source. Refuse instead.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
coderabbitai[bot]
coderabbitaiBot
suggested changes
Aug 9, 2026
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/devpc-managed-release.yml:
- Line 160: Update the release-tag logic near the version input handling to
validate the base version against the versions in both apps/server/package.json
and apps/web/package.json before publishing. Derive the tag from the checked-out
package metadata, or fail when the supplied input’s base version does not match
both packages, so a mismatched artifact cannot be published under an incorrect
devpc tag.

🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
  •  Push a commit to this branch (recommended)
  •  Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: d64e421a-3d9c-4b1d-adad-f74cd391e7aa
📥 Commits
Reviewing files that changed from the base of the PR and between 8818409 and 14d02b3.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:ad596f7796
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Pass the dispatch version via env and cross-check package versions
895f314
The version input now reaches the publish script through the job
environment instead of template expansion, so it cannot expand into
shell syntax. Its base version is also compared against the versions
in apps/server and apps/web package.json, refusing to label an
artifact with a version the packages do not carry.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@claude
Fail the publish when the existing-tag lookup itself errors
4e96e9e
The tag-mismatch guard resolved the tag with gh api and swallowed
every failure as absence, so a transient lookup error could still
publish under a stale tag. git ls-remote distinguishes the two:
empty output means the tag is absent, a nonzero exit fails the step.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@logancsack
logancsack
merged commit 872106e
into
mainAug 9, 2026

12 checks passed

@logancsacklogancsack
mentioned this pull request
Aug 9, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@chatgpt-codex-connectorchatgpt-codex-connector[bot]chatgpt-codex-connector[bot] left review comments

+1 more reviewer

@coderabbitaicoderabbitai[bot]coderabbitai[bot] approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@logancsack@claude

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
Publish release assets from manually dispatched devpc release runs - #59
Merged
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Aug 9, 2026
Merged
Publish release assets from manually dispatched devpc release runs#59
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Conversation
@logancsack
@logancsacklogancsack
commented
Aug 9, 2026•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Owner
A workflow_dispatch run of devpc-managed-release.yml built and verified the artifact but published nothing — the release step was gated on tag refs only, so the dispatch path could not produce the checksummed GitHub release that the workspace pin (config/t3code-release.json in remote-dev) consumes.
Dispatch runs now publish too: the devpc-v tag is derived from the version input (0.0.28-devpc.54 → devpc-v0.0.28.54) and gh release create --target "$GITHUB_SHA" creates the tag at the built commit. Tag-push runs are unchanged.
Motivation right now: devpc-v0.0.28.54 needs to be cut from main (8818409, PR #58) and the environment driving this release can push branches but not tags, so the dispatch path is the release mechanism.
Generated by Claude Code
Summary by CodeRabbit
  • Chores
    • Release workflows can now be started manually with a specified version.
    • Releases triggered by tags or manual runs are created from the appropriate commit.
    • Published packages and checksums now include automatically generated release notes.
@claude
Publish release assets from manually dispatched devpc release runs
14d02b3
A workflow_dispatch run built and verified the artifact but published
nothing, leaving the dispatch path unable to produce the checksummed
release the workspace pin consumes. Dispatch runs now create the release
too, deriving the devpc-v tag from the version input and letting gh create
the tag at the built commit.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@github-actionsgithub-actionsBot
added

size:S

vouch:trusted
PR author is trusted by repo permissions or the VOUCHED list.
labels
Aug 9, 2026
@coderabbitai
coderabbitaiBot
commented
Aug 9, 2026•

edited

Loading

Copy link


Copy Markdown

Review Change Stack
Warning
Review limit reached
@logancsack, you've reached your PR review limit, so we couldn't start this review.
Next review available in:51 minutes
You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.
How can I continue?
After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.
To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.
How do review limits work?
CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.
For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.
Please refer docs for additional details.
Review details
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 2b1befb5-6280-4efb-9eea-7e0e4826f6d5
📥 Commits
Reviewing files that changed from the base of the PR and between 14d02b3 and 4e96e9e.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
📝 Walkthrough
Walkthrough
The release workflow now supports tag pushes and manual dispatches. Manual dispatches convert the supplied version into a devpc-v... tag at GITHUB_SHA. Tag pushes use GITHUB_REF_NAME. Both paths upload release artifacts with generated notes.
Changes
DevPC release publishing
Layer / File(s)Summary
Release trigger and publishing flow
.github/workflows/devpc-managed-release.yml		Manual runs create a release tag from the version input at GITHUB_SHA. Tag-triggered runs retain GITHUB_REF_NAME. Both paths upload the package and checksum with generated release notes.
Estimated code review effort: 2 (Simple) | ~10 minutes
Poem
A rabbit checks the release gate,

Tags hop out and versions wait.

The package and checksum join the run,

Notes bloom softly in the sun.
GITHUB_SHA marks where releases grow.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly describes the main change: publishing release assets from manually dispatched DevPC release runs.
Description check✅ PassedThe description explains what changed and why, including dispatch behavior and release tag creation; the optional checklist is omitted.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/devpc-release-dispatch-publish
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:14d02b3d00
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Validate dispatch version and guard existing-tag mismatches
ad596f7
A dispatch run now rejects a version input that does not match the
N.N.N-devpc.N shape, and resolves any pre-existing release tag before
publishing: gh release create's --target only applies when the tag is
absent, so an existing tag at another commit would have silently
labeled this run's assets with the wrong source. Refuse instead.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
coderabbitai[bot]
coderabbitaiBot
suggested changes
Aug 9, 2026
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/devpc-managed-release.yml:
- Line 160: Update the release-tag logic near the version input handling to
validate the base version against the versions in both apps/server/package.json
and apps/web/package.json before publishing. Derive the tag from the checked-out
package metadata, or fail when the supplied input’s base version does not match
both packages, so a mismatched artifact cannot be published under an incorrect
devpc tag.

🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
  •  Push a commit to this branch (recommended)
  •  Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: d64e421a-3d9c-4b1d-adad-f74cd391e7aa
📥 Commits
Reviewing files that changed from the base of the PR and between 8818409 and 14d02b3.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:ad596f7796
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Pass the dispatch version via env and cross-check package versions
895f314
The version input now reaches the publish script through the job
environment instead of template expansion, so it cannot expand into
shell syntax. Its base version is also compared against the versions
in apps/server and apps/web package.json, refusing to label an
artifact with a version the packages do not carry.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@claude
Fail the publish when the existing-tag lookup itself errors
4e96e9e
The tag-mismatch guard resolved the tag with gh api and swallowed
every failure as absence, so a transient lookup error could still
publish under a stale tag. git ls-remote distinguishes the two:
empty output means the tag is absent, a nonzero exit fails the step.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@logancsack
logancsack
merged commit 872106e
into
mainAug 9, 2026

12 checks passed

@logancsacklogancsack
mentioned this pull request
Aug 9, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@chatgpt-codex-connectorchatgpt-codex-connector[bot]chatgpt-codex-connector[bot] left review comments

+1 more reviewer

@coderabbitaicoderabbitai[bot]coderabbitai[bot] approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@logancsack@claude

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Publish release assets from manually dispatched devpc release runs - #59
Merged
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Aug 9, 2026
Merged
Publish release assets from manually dispatched devpc release runs#59
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Conversation
@logancsack
@logancsacklogancsack
commented
Aug 9, 2026•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Owner
A workflow_dispatch run of devpc-managed-release.yml built and verified the artifact but published nothing — the release step was gated on tag refs only, so the dispatch path could not produce the checksummed GitHub release that the workspace pin (config/t3code-release.json in remote-dev) consumes.
Dispatch runs now publish too: the devpc-v tag is derived from the version input (0.0.28-devpc.54 → devpc-v0.0.28.54) and gh release create --target "$GITHUB_SHA" creates the tag at the built commit. Tag-push runs are unchanged.
Motivation right now: devpc-v0.0.28.54 needs to be cut from main (8818409, PR #58) and the environment driving this release can push branches but not tags, so the dispatch path is the release mechanism.
Generated by Claude Code
Summary by CodeRabbit
  • Chores
    • Release workflows can now be started manually with a specified version.
    • Releases triggered by tags or manual runs are created from the appropriate commit.
    • Published packages and checksums now include automatically generated release notes.
@claude
Publish release assets from manually dispatched devpc release runs
14d02b3
A workflow_dispatch run built and verified the artifact but published
nothing, leaving the dispatch path unable to produce the checksummed
release the workspace pin consumes. Dispatch runs now create the release
too, deriving the devpc-v tag from the version input and letting gh create
the tag at the built commit.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@github-actionsgithub-actionsBot
added

size:S

vouch:trusted
PR author is trusted by repo permissions or the VOUCHED list.
labels
Aug 9, 2026
@coderabbitai
coderabbitaiBot
commented
Aug 9, 2026•

edited

Loading

Copy link


Copy Markdown

Review Change Stack
Warning
Review limit reached
@logancsack, you've reached your PR review limit, so we couldn't start this review.
Next review available in:51 minutes
You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.
How can I continue?
After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.
To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.
How do review limits work?
CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.
For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.
Please refer docs for additional details.
Review details
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 2b1befb5-6280-4efb-9eea-7e0e4826f6d5
📥 Commits
Reviewing files that changed from the base of the PR and between 14d02b3 and 4e96e9e.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
📝 Walkthrough
Walkthrough
The release workflow now supports tag pushes and manual dispatches. Manual dispatches convert the supplied version into a devpc-v... tag at GITHUB_SHA. Tag pushes use GITHUB_REF_NAME. Both paths upload release artifacts with generated notes.
Changes
DevPC release publishing
Layer / File(s)Summary
Release trigger and publishing flow
.github/workflows/devpc-managed-release.yml		Manual runs create a release tag from the version input at GITHUB_SHA. Tag-triggered runs retain GITHUB_REF_NAME. Both paths upload the package and checksum with generated release notes.
Estimated code review effort: 2 (Simple) | ~10 minutes
Poem
A rabbit checks the release gate,

Tags hop out and versions wait.

The package and checksum join the run,

Notes bloom softly in the sun.
GITHUB_SHA marks where releases grow.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly describes the main change: publishing release assets from manually dispatched DevPC release runs.
Description check✅ PassedThe description explains what changed and why, including dispatch behavior and release tag creation; the optional checklist is omitted.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/devpc-release-dispatch-publish
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:14d02b3d00
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Validate dispatch version and guard existing-tag mismatches
ad596f7
A dispatch run now rejects a version input that does not match the
N.N.N-devpc.N shape, and resolves any pre-existing release tag before
publishing: gh release create's --target only applies when the tag is
absent, so an existing tag at another commit would have silently
labeled this run's assets with the wrong source. Refuse instead.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
coderabbitai[bot]
coderabbitaiBot
suggested changes
Aug 9, 2026
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/devpc-managed-release.yml:
- Line 160: Update the release-tag logic near the version input handling to
validate the base version against the versions in both apps/server/package.json
and apps/web/package.json before publishing. Derive the tag from the checked-out
package metadata, or fail when the supplied input’s base version does not match
both packages, so a mismatched artifact cannot be published under an incorrect
devpc tag.

🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
  •  Push a commit to this branch (recommended)
  •  Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: d64e421a-3d9c-4b1d-adad-f74cd391e7aa
📥 Commits
Reviewing files that changed from the base of the PR and between 8818409 and 14d02b3.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:ad596f7796
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Pass the dispatch version via env and cross-check package versions
895f314
The version input now reaches the publish script through the job
environment instead of template expansion, so it cannot expand into
shell syntax. Its base version is also compared against the versions
in apps/server and apps/web package.json, refusing to label an
artifact with a version the packages do not carry.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@claude
Fail the publish when the existing-tag lookup itself errors
4e96e9e
The tag-mismatch guard resolved the tag with gh api and swallowed
every failure as absence, so a transient lookup error could still
publish under a stale tag. git ls-remote distinguishes the two:
empty output means the tag is absent, a nonzero exit fails the step.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@logancsack
logancsack
merged commit 872106e
into
mainAug 9, 2026

12 checks passed

@logancsacklogancsack
mentioned this pull request
Aug 9, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@chatgpt-codex-connectorchatgpt-codex-connector[bot]chatgpt-codex-connector[bot] left review comments

+1 more reviewer

@coderabbitaicoderabbitai[bot]coderabbitai[bot] approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@logancsack@claude

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Publish release assets from manually dispatched devpc release runs - #59
Merged
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Aug 9, 2026
Merged
Publish release assets from manually dispatched devpc release runs#59
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Conversation
@logancsack
@logancsacklogancsack
commented
Aug 9, 2026•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Owner
A workflow_dispatch run of devpc-managed-release.yml built and verified the artifact but published nothing — the release step was gated on tag refs only, so the dispatch path could not produce the checksummed GitHub release that the workspace pin (config/t3code-release.json in remote-dev) consumes.
Dispatch runs now publish too: the devpc-v tag is derived from the version input (0.0.28-devpc.54 → devpc-v0.0.28.54) and gh release create --target "$GITHUB_SHA" creates the tag at the built commit. Tag-push runs are unchanged.
Motivation right now: devpc-v0.0.28.54 needs to be cut from main (8818409, PR #58) and the environment driving this release can push branches but not tags, so the dispatch path is the release mechanism.
Generated by Claude Code
Summary by CodeRabbit
  • Chores
    • Release workflows can now be started manually with a specified version.
    • Releases triggered by tags or manual runs are created from the appropriate commit.
    • Published packages and checksums now include automatically generated release notes.
@claude
Publish release assets from manually dispatched devpc release runs
14d02b3
A workflow_dispatch run built and verified the artifact but published
nothing, leaving the dispatch path unable to produce the checksummed
release the workspace pin consumes. Dispatch runs now create the release
too, deriving the devpc-v tag from the version input and letting gh create
the tag at the built commit.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@github-actionsgithub-actionsBot
added

size:S

vouch:trusted
PR author is trusted by repo permissions or the VOUCHED list.
labels
Aug 9, 2026
@coderabbitai
coderabbitaiBot
commented
Aug 9, 2026•

edited

Loading

Copy link


Copy Markdown

Review Change Stack
Warning
Review limit reached
@logancsack, you've reached your PR review limit, so we couldn't start this review.
Next review available in:51 minutes
You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.
How can I continue?
After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.
To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.
How do review limits work?
CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.
For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.
Please refer docs for additional details.
Review details
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 2b1befb5-6280-4efb-9eea-7e0e4826f6d5
📥 Commits
Reviewing files that changed from the base of the PR and between 14d02b3 and 4e96e9e.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
📝 Walkthrough
Walkthrough
The release workflow now supports tag pushes and manual dispatches. Manual dispatches convert the supplied version into a devpc-v... tag at GITHUB_SHA. Tag pushes use GITHUB_REF_NAME. Both paths upload release artifacts with generated notes.
Changes
DevPC release publishing
Layer / File(s)Summary
Release trigger and publishing flow
.github/workflows/devpc-managed-release.yml		Manual runs create a release tag from the version input at GITHUB_SHA. Tag-triggered runs retain GITHUB_REF_NAME. Both paths upload the package and checksum with generated release notes.
Estimated code review effort: 2 (Simple) | ~10 minutes
Poem
A rabbit checks the release gate,

Tags hop out and versions wait.

The package and checksum join the run,

Notes bloom softly in the sun.
GITHUB_SHA marks where releases grow.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly describes the main change: publishing release assets from manually dispatched DevPC release runs.
Description check✅ PassedThe description explains what changed and why, including dispatch behavior and release tag creation; the optional checklist is omitted.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/devpc-release-dispatch-publish
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:14d02b3d00
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Validate dispatch version and guard existing-tag mismatches
ad596f7
A dispatch run now rejects a version input that does not match the
N.N.N-devpc.N shape, and resolves any pre-existing release tag before
publishing: gh release create's --target only applies when the tag is
absent, so an existing tag at another commit would have silently
labeled this run's assets with the wrong source. Refuse instead.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
coderabbitai[bot]
coderabbitaiBot
suggested changes
Aug 9, 2026
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/devpc-managed-release.yml:
- Line 160: Update the release-tag logic near the version input handling to
validate the base version against the versions in both apps/server/package.json
and apps/web/package.json before publishing. Derive the tag from the checked-out
package metadata, or fail when the supplied input’s base version does not match
both packages, so a mismatched artifact cannot be published under an incorrect
devpc tag.

🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
  •  Push a commit to this branch (recommended)
  •  Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: d64e421a-3d9c-4b1d-adad-f74cd391e7aa
📥 Commits
Reviewing files that changed from the base of the PR and between 8818409 and 14d02b3.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:ad596f7796
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Pass the dispatch version via env and cross-check package versions
895f314
The version input now reaches the publish script through the job
environment instead of template expansion, so it cannot expand into
shell syntax. Its base version is also compared against the versions
in apps/server and apps/web package.json, refusing to label an
artifact with a version the packages do not carry.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@claude
Fail the publish when the existing-tag lookup itself errors
4e96e9e
The tag-mismatch guard resolved the tag with gh api and swallowed
every failure as absence, so a transient lookup error could still
publish under a stale tag. git ls-remote distinguishes the two:
empty output means the tag is absent, a nonzero exit fails the step.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@logancsack
logancsack
merged commit 872106e
into
mainAug 9, 2026

12 checks passed

@logancsacklogancsack
mentioned this pull request
Aug 9, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@chatgpt-codex-connectorchatgpt-codex-connector[bot]chatgpt-codex-connector[bot] left review comments

+1 more reviewer

@coderabbitaicoderabbitai[bot]coderabbitai[bot] approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@logancsack@claude

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
Publish release assets from manually dispatched devpc release runs - #59
Merged
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Aug 9, 2026
Merged
Publish release assets from manually dispatched devpc release runs#59
logancsack merged 4 commits into
mainfrom 
fix/devpc-release-dispatch-publish
Conversation
@logancsack
@logancsacklogancsack
commented
Aug 9, 2026•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Owner
A workflow_dispatch run of devpc-managed-release.yml built and verified the artifact but published nothing — the release step was gated on tag refs only, so the dispatch path could not produce the checksummed GitHub release that the workspace pin (config/t3code-release.json in remote-dev) consumes.
Dispatch runs now publish too: the devpc-v tag is derived from the version input (0.0.28-devpc.54 → devpc-v0.0.28.54) and gh release create --target "$GITHUB_SHA" creates the tag at the built commit. Tag-push runs are unchanged.
Motivation right now: devpc-v0.0.28.54 needs to be cut from main (8818409, PR #58) and the environment driving this release can push branches but not tags, so the dispatch path is the release mechanism.
Generated by Claude Code
Summary by CodeRabbit
  • Chores
    • Release workflows can now be started manually with a specified version.
    • Releases triggered by tags or manual runs are created from the appropriate commit.
    • Published packages and checksums now include automatically generated release notes.
@claude
Publish release assets from manually dispatched devpc release runs
14d02b3
A workflow_dispatch run built and verified the artifact but published
nothing, leaving the dispatch path unable to produce the checksummed
release the workspace pin consumes. Dispatch runs now create the release
too, deriving the devpc-v tag from the version input and letting gh create
the tag at the built commit.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@github-actionsgithub-actionsBot
added

size:S

vouch:trusted
PR author is trusted by repo permissions or the VOUCHED list.
labels
Aug 9, 2026
@coderabbitai
coderabbitaiBot
commented
Aug 9, 2026•

edited

Loading

Copy link


Copy Markdown

Review Change Stack
Warning
Review limit reached
@logancsack, you've reached your PR review limit, so we couldn't start this review.
Next review available in:51 minutes
You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.
How can I continue?
After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.
To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.
How do review limits work?
CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.
For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.
Please refer docs for additional details.
Review details
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 2b1befb5-6280-4efb-9eea-7e0e4826f6d5
📥 Commits
Reviewing files that changed from the base of the PR and between 14d02b3 and 4e96e9e.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
📝 Walkthrough
Walkthrough
The release workflow now supports tag pushes and manual dispatches. Manual dispatches convert the supplied version into a devpc-v... tag at GITHUB_SHA. Tag pushes use GITHUB_REF_NAME. Both paths upload release artifacts with generated notes.
Changes
DevPC release publishing
Layer / File(s)Summary
Release trigger and publishing flow
.github/workflows/devpc-managed-release.yml		Manual runs create a release tag from the version input at GITHUB_SHA. Tag-triggered runs retain GITHUB_REF_NAME. Both paths upload the package and checksum with generated release notes.
Estimated code review effort: 2 (Simple) | ~10 minutes
Poem
A rabbit checks the release gate,

Tags hop out and versions wait.

The package and checksum join the run,

Notes bloom softly in the sun.
GITHUB_SHA marks where releases grow.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly describes the main change: publishing release assets from manually dispatched DevPC release runs.
Description check✅ PassedThe description explains what changed and why, including dispatch behavior and release tag creation; the optional checklist is omitted.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/devpc-release-dispatch-publish
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:14d02b3d00
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Validate dispatch version and guard existing-tag mismatches
ad596f7
A dispatch run now rejects a version input that does not match the
N.N.N-devpc.N shape, and resolves any pre-existing release tag before
publishing: gh release create's --target only applies when the tag is
absent, so an existing tag at another commit would have silently
labeled this run's assets with the wrong source. Refuse instead.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
coderabbitai[bot]
coderabbitaiBot
suggested changes
Aug 9, 2026
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/devpc-managed-release.yml:
- Line 160: Update the release-tag logic near the version input handling to
validate the base version against the versions in both apps/server/package.json
and apps/web/package.json before publishing. Derive the tag from the checked-out
package metadata, or fail when the supplied input’s base version does not match
both packages, so a mismatched artifact cannot be published under an incorrect
devpc tag.

🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
  •  Push a commit to this branch (recommended)
  •  Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: d64e421a-3d9c-4b1d-adad-f74cd391e7aa
📥 Commits
Reviewing files that changed from the base of the PR and between 8818409 and 14d02b3.
📒 Files selected for processing (1)
  • .github/workflows/devpc-managed-release.yml
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

chatgpt-codex-connector[bot]
chatgpt-codex-connectorBot
reviewed
Aug 9, 2026
View reviewed changes
@chatgpt-codex-connectorchatgpt-codex-connectorBot
left a comment


Copy link


Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:ad596f7796
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Comment thread.github/workflows/devpc-managed-release.yml
Outdated

Comment thread.github/workflows/devpc-managed-release.yml
Outdated

@claude
Pass the dispatch version via env and cross-check package versions
895f314
The version input now reaches the publish script through the job
environment instead of template expansion, so it cannot expand into
shell syntax. Its base version is also compared against the versions
in apps/server and apps/web package.json, refusing to label an
artifact with a version the packages do not carry.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@claude
Fail the publish when the existing-tag lookup itself errors
4e96e9e
The tag-mismatch guard resolved the tag with gh api and swallowed
every failure as absence, so a transient lookup error could still
publish under a stale tag. git ls-remote distinguishes the two:
empty output means the tag is absent, a nonzero exit fails the step.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eomHzc8Ese8TSm5WZBCX9
@logancsack
logancsack
merged commit 872106e
into
mainAug 9, 2026

12 checks passed

@logancsacklogancsack
mentioned this pull request
Aug 9, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@chatgpt-codex-connectorchatgpt-codex-connector[bot]chatgpt-codex-connector[bot] left review comments

+1 more reviewer

@coderabbitaicoderabbitai[bot]coderabbitai[bot] approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees


No one assigned


Labels

size:Mvouch:trustedPR author is trusted by repo permissions or the VOUCHED list.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@logancsack@claude