Uh oh!
There was an error while loading. Please reload this page.
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.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: ModbusScope/ModbusSim
Length of output: 3853
🌐 Web query:
softprops/action-gh-release v3 existing assets overwrite files tag_name💡 Result:
In softprops/action-gh-release v3, existing assets are overwritten by default when a new file with the same name is uploaded to the same release tag [1][2][3]. This behavior is controlled by the overwrite_files input, which is a boolean that defaults to true [1][4]. Regarding your query: - Overwriting assets: The action includes logic to handle overwriting files if they already exist [2][4]. If an upload attempt fails because an asset with the same name already exists, the action is designed to identify the existing asset, remove it, and retry the upload [5]. - tag_name: When a tag_name is specified, the action checks for an existing release associated with that tag [2][4]. If one exists, the action updates that release with the provided assets rather than creating a new one [2][4]. If release information keys (such as name, body, or prerelease status) are not explicitly set, the existing release will retain its original information [2][4]. Note: While the default behavior is to overwrite, race conditions may occasionally occur if multiple workflows attempt to upload assets with the same name to the same release simultaneously [5][6]. The action has implemented retries to mitigate these issues [5].
Citations:
Serialise overlapping
latest-devpublishes.When two
masterruns executepackageconcurrently, an older run can movelatest-devbackwards and overwrite same-named assets in the shared release. Add package-job concurrency withcancel-in-progress: true, or reject runs that are no longer the newest.🧰 Tools
🪛 zizmor (1.29.0)
[warning] 1-129: overly broad permissions (excessive-permissions): default permissions used due to no permissions: block
(excessive-permissions)
🤖 Prompt for AI Agents