-
Notifications
You must be signed in to change notification settings - Fork 884
Fail on JavaScript run script Dockerfile conflict #16969
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
mitchdenny
merged 7 commits into
main
from
sebastienros/sebros-fix-javascriptapp-entrypoint
May 19, 2026
+254
−7
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
e9dca1a
Fail when JavaScript run script conflicts with Dockerfile
sebastienros 4ca0c7a
Validate JavaScript Dockerfile run scripts in pipeline
sebastienros 404e13b
Fix Dockerfile publish tests for run script validation
sebastienros 02cec45
Merge branch 'main' into sebastienros/sebros-fix-javascriptapp-entryp…
sebastienros d182e0c
Remove manifest step coupling from JS validation
sebastienros df796c4
Refine JS Dockerfile run-script conflict detection
64ea719
Merge remote-tracking branch 'origin/main' into sebastienros/sebros-f…
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hasExplicitRunScriptcan be set purely byrunScript.Args.Length > 0, even whenrunScript.ScriptNameequals the default"dev". But the thrown message only mentionsrunScriptNameandWithRunScript(the script name), not the args. So this:fails with
... is configured to run script 'dev', but publish is using the existing Dockerfile ...— no mention of the args, which are the actual reason for the failure. Verified locally: the message produced for the args-only case is identical to the case where the user passed a non-default script name.Suggested fix: when the trigger is
runScript.Args.Length > 0, include the args in the message (e.g.... is configured to run script 'dev' with args [--port, 8080], ...).