Skip to content

Fix init control layout and preserve hardware launch fields - #57

Closed
chen21019 wants to merge 1 commit into
mainfrom
fix/init-control-layout-1.6.104
Closed

Fix init control layout and preserve hardware launch fields#57
chen21019 wants to merge 1 commit into
mainfrom
fix/init-control-layout-1.6.104

Conversation

@chen21019

Copy link
Copy Markdown

Result

  • keep the init checkbox inside its own resource grid cell on create and upgrade forms
  • retain explicit launchConfig.runInit binding
  • cover every hardware/runtime field in create and upgrade payloads
  • publish the pure numeric Web Console version 1.6.104

Validation

  • full Chrome suite: 425 passed, 0 failed
  • hardware-focused suite: 20 passed, 0 failed
  • npm audit: 0 vulnerabilities
  • two production packages were byte-identical

@chen21019
chen21019 requested a review from a team as a code owner September 10, 2026 17:37
@chen21019
chen21019 force-pushed the fix/init-control-layout-1.6.104 branch from 4561939 to c870021 Compare September 10, 2026 17:40
@chen21019
chen21019 enabled auto-merge (squash) September 10, 2026 17:47
@chen21019
chen21019 disabled auto-merge September 10, 2026 17:53
@chen21019

Copy link
Copy Markdown
Author

Superseded by an identical-tree GitHub-signed commit so required-signature protection remains enforced.

@chen21019 chen21019 closed this Sep 10, 2026
@chen21019
chen21019 deleted the fix/init-control-layout-1.6.104 branch September 10, 2026 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant