qo
Qovery
GitHub
console
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
fix/blueprint-rc-tag-support
Runs and Agents
Configuration
Self-Healing CI
Project Graph
Circular Dependencies
Enterprise
Resource Usage
Analysis
Conformance
Enterprise
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
fix(blueprint): only read the pinned branch when it is shaped like a tag What: Add `isBlueprintTag` and gate the local-tag fallback on it, so a branch that is not `{PROVIDER}/{service}/{major}/{version}` is ignored rather than read. Why: Both tag accessors are positional — `getBlueprintServiceVersion` takes the second-to-last segment — so a three-segment branch such as `AWS/s3/1.2.3` would have rendered `vs3`, and a plain branch name would have rendered the repository owner. Wrong output is worse than none, and unlike `current_tag` the branch is read off the service rather than handed over by an API that already validated it. The shape checked here is the one q-core enforces before it will read a tag at all. Notes: - This should not fire in practice: the engine writes the blueprint tag verbatim as the branch, q-core rejects any tag that is not four segments, and the console blocks editing the git source of a blueprint-backed service. The guard is for when one of those stops holding. - It covers the list cell as well as the header — both resolve their tag through the same hook. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
nx run console:build --parallel=3 --configuration=development
⌘K
Succeeded
nx run console:build --parallel=3 --configuration=development
Click to copy
read-write
access token used
867740cf
2909