fix(ci): prevent npm-publish chmod step from failing on missing binaries#11
Merged
StefanSteiner merged 1 commit intoMay 18, 2026
Merged
Conversation
The "Restore executable bits" step failed because `[[ -f "$f" ]] && chmod +x "$f"` returns exit code 1 under `set -euo pipefail` when the file doesn't exist (e.g. platform dirs without artifacts, or Windows .exe binaries not matching extensionless names). Add `|| true` and include .exe variants.
Merged
StefanSteiner
added a commit
that referenced
this pull request
May 18, 2026
🤖 I have created a release *beep* *boop* --- <details><summary>0.1.2</summary> ## [0.1.2](v0.1.1...v0.1.2) (2026-05-18) ### Bug Fixes * **ci:** include README.md in hyperdb-mcp npm package ([c8ccc22](c8ccc22)) * **ci:** include README.md in hyperdb-mcp npm package ([#12](#12)) ([b1ddb33](b1ddb33)) * **ci:** prevent npm-publish chmod step from failing on missing binaries ([2708ee4](2708ee4)) * **ci:** prevent npm-publish chmod step from failing on missing binaries ([#11](#11)) ([bc9bee5](bc9bee5)) * **ci:** remove brew rust on macOS before installing toolchain ([b331607](b331607)) * **ci:** remove brew-rust uninstall steps that delete cargo/rustc on new image ([af798f1](af798f1)) * **ci:** restructure release-please config for workspace version inheritance ([d5ad018](d5ad018)) * **ci:** restructure release-please config for workspace version inheritance ([#13](#13)) ([fd18a8b](fd18a8b)) * **ci:** use simple release-type to avoid Cargo workspace member walking ([3884162](3884162)) * **ci:** use simple release-type to avoid Cargo workspace member walking ([#14](#14)) ([42f0524](42f0524)) </details> <details><summary>0.1.2</summary> ## [0.1.2](v0.1.1...v0.1.2) (2026-05-18) ### Bug Fixes * **ci:** include README.md in hyperdb-mcp npm package ([c8ccc22](c8ccc22)) * **ci:** include README.md in hyperdb-mcp npm package ([#12](#12)) ([b1ddb33](b1ddb33)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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
[[ -f "$f" ]] && chmod +x "$f"returns 1 underset -euo pipefailwhen the file doesn't exist (platform dirs without artifacts, or Windows.exebinaries not matching extensionless names)|| trueto prevent exit-code leak and include.exevariants for Windowshyperdb-mcp/README.mdinto thehyperdb-mcp/npm/publish directory so npmjs.com renders a package README instead of a blank pageTest plan