Repository navigation
fix(release): run pinned async versions on their own variables, map CLI key-creation errors, show GitLab tokens as the current block - #9862
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
All reported issues were addressed across 15 files
Reply with feedback, questions, or to request a fix.
Turn on auto-fix | Re-trigger cubic
[Medium impact] The current diff appears safe to merge. SummaryThis diff makes three small behavior fixes and clarifies a Dockerfile comment:
No new actionable issues were found. Firecrawl changes described in the PR are not part of the current diff. Reviews (3) · Last reviewed commit: "fix(release): run pinned async versions ..." · Reviewed by Greptile |
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
af4d72d to
33f650f
Compare
…LI key-creation errors, show GitLab tokens as the current block
33f650f to
3ba0ef7
Compare
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
Summary
run.versionasync runs (new in feat(api): run a pinned deployment version and expose paused run points in v2 #9854, not yet released) set a pin; unpinned async, schedule and webhook runs keepresolveDeployedRunVariablesunchangedScoped to what no other release-audit PR covers: crawl depth is on staging via #9860; workflow access middleware, route policies and CONTRIBUTING are in #9858. Firecrawl search
sourceshandling is left out pending a product decision (the block never forwardssourcestoday).Type of Change
Testing
lib/integrations/credential-display.test.tspassesChecklist
test-auditauthoring gate)