feat(build): add --dynamic flag and infobase.unlock_code config#2
Open
steel-code-agent wants to merge 1 commit into
Open
feat(build): add --dynamic flag and infobase.unlock_code config#2steel-code-agent wants to merge 1 commit into
steel-code-agent wants to merge 1 commit into
Conversation
- CLI flag `--dynamic` for `build` enables /UpdateDBCfg -Dynamic+ - New config field `build.dynamicUpdate` (default false), CLI overrides config - New config field `infobase.unlock_code` propagates /UC <value> to DESIGNER - Mask unlock_code in command-render logs like password (/UC ***) - Propagate dynamic flag through BuildRequest, McpBuildProjectRequest and the execute_source_set_step pipeline; `load` and tool-extension flows keep the historical static update - Bump version 0.4.2 -> 0.5.0 - Regenerate JSON schemas for v8project.yaml / v8project.local.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Sync our fork's
masterwith the--dynamic+infobase.unlock_codework (commitb04926f) that already lives upstream-bound on PR alkoleft#8.--dynamicCLI flag forbuild→/UpdateDBCfg -Dynamic+infobase.unlock_codeconfig →/UC <value>to DESIGNER, masked in logsUpstream
PR in alkoleft: alkoleft#8
Why a separate PR for our fork
Direct push to
masteris blocked by the agent-environment policy. This PR just merges the commit that has been sitting on localmasterfor a day, so our fork'smastermatches what's already open for review upstream.