Bump actions/upload-artifact from 5 to 6 #4
Conversation
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
So the header subdir used for the `install-headers` target is scallop otherwise it would overlap with the regular bash package when plugin support is enabled (which installs the headers). Also, this changes $PACKAGE_VERSION to the X.Y.Z.DATE format used by scallop.
Previously when building libraries for scallop, the configure target would trigger autoconf to be run unnecessarily as the bundled configure script should up-to-date.
…Level This makes deferred vs immediate expansion work as expected for other variables using $(PatchLevel).
And rename main() to bash_main() in order to use it externally when library support is enabled.
About the security issues with mktemp.
That allows external code to register builtins internally instead of always having to using dynamic loading.
With the builtin being used if it exists instead of the function.
Bash uses an extensive amount of global state and when used as a library init/reset actions are required for regular operation.
Without this both leak their underlying array data whenever lib_reset() is called.
Bash uses setjmp/longjmp for error, interrupt, and signal handling cases and thus initializes jump targets in main() which doesn't get called when used as a library. Adding jump targets in the main entry points (sourcing and execution) allows returning proper error codes during library operation and avoids issues with unwinding across rust frames (which is currently UB and generally causes segfaults) when using scallop rust support. Without this, a segfault occurs if a file with errors is sourced under library usage and `set -e` enabled since no top level jump target is set and parse_and_execute() tries to longjmp to a NULL target. Note that the call stack is tracked from scallop so reentrant calls jump back to where they entered and not the initial call's entry point.
Instead of always dumping them into stderr.
Used via external library to inject errors into bash across process boundaries (e.g. erroring out from subshells).
Installing a SIGCHLD handler by default breaks pkgcraft unit tests that spawn child processes and use wait() or waitpid() to wait for completion, e.g. tests for builtins such as `econf`. When enabled by default the tests fail with ECHILD (errno 10) when trying to wait on child processes since the installed signal handler gets control instead during child termination.
That allows easily reverting set_var_read_only() settings when toggling restricted mode.
Without this the process environment isn't inherited and the bash initialization methods unset everything.
Instead of raising an error. The exit status of the command should be enough to signify failure. This avoids the issue where `declare -p UNDEFINED_VAR` is being used to determine if a variable is defined causing errors when sourcing the related file or string.
… exec This allows externally registered special builtins to always override functions even when bash isn't built with strict posix mode enabled. This will also have the affect that special builtins native to bash, e.g. exit and source (see the full list via `enable -s`), won't be able to be overridden by functions which in our case shouldn't matter and probably is a good thing anyway.
These should be used externally to build with the options required by scallop otherwise it's unsupported when used for pkgcraft.
This makes the option name handling match get_minus_o_opts() in the `set` builtin and is what the the only usage for get_shopt_options() in pcomplete.c expects as it explicitly doesn't free the list members the same as it does for the set options list.
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 5 to 6. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v5...v6) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps actions/upload-artifact from 5 to 6.
Release notes
Sourced from actions/upload-artifact's releases.
Commits
b7c566aMerge pull request #745 from actions/upload-artifact-v6-releasee516bc8docs: correct description of Node.js 24 support in READMEddc45eddocs: update README to correct action name for Node.js 24 support615b319chore: release v6.0.0 for Node.js 24 support017748bMerge pull request #744 from actions/fix-storage-blob38d4c79chore: rebuild dist7d27270chore: add missing license cache files for@actions/core,@actions/io, and mi...5f643d3chore: update license files for@actions/artifact@5.0.1 dependencies1df1684chore: update package-lock.json with@actions/artifact@5.0.1b5b1a91fix: update@actions/artifactto ^5.0.0 for Node.js 24 punycode fixDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)