chore(ci): bump publish-docs orb to @0.5#1610
Merged
Merged
Conversation
`infinitered/publish-docs@0.4` (resolves to v0.4.13) had a bug where multiline / colon-containing commit message bodies polluted $BASH_ENV when sourced, producing a flood of "command not found" errors and ultimately failing the publish_docs job with `Error: Not a GitHub URL`. Hit this on the master push for #1609. Diagnosis: the orb wrote unescaped multi-line content to $BASH_ENV via `echo "export VAR=\"${VAL}\""`, which bash then evaluated as commands at the start of the next step. Fixed upstream in infinitered/orb-publish-docs#40 (replaces those echoes with `printf 'export VAR=%q\n' "$VAL"`) and just released as v0.5.1. Diff `@0.4 → @0.5.1` is purely internal scripts — zero public API change. All existing job/parameter usage in this repo (build_docs / publish_docs with the `ir_docs_config` params) remains compatible. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
infinitered-circleci
added a commit
to infinitered/ir-docs
that referenced
this pull request
May 4, 2026
## Please verify the following: - [x] `yarn build-and-test:local` passes - [ ] I have added tests for any new features, if relevant - [x] `README.md` (or relevant documentation) has been updated with your changes ## Describe your PR Bumps the `infinitered/publish-docs` orb from `@0.4` (resolves to v0.4.13) to `@0.5` (resolves to v0.5.1). This unbreaks `publish-docs/publish_docs` on master pushes when the merge commit body contains markdown / multi-line content. ### Why The orb's v0.4.13 wrote unescaped multi-line shell content to `$BASH_ENV` via `echo "export VAR=\"$VAL\""`. When the merge commit's body had colons (e.g. inline JSON snippets) or newlines, bash interpreted each line as a command after sourcing `$BASH_ENV` at the start of the next step. Symptom on the master push for #1609: ``` /tmp/.bash_env-...-build: line 39: README.md: command not found /tmp/.bash_env-...-build: line 39: NPM_TOKEN: command not found ... [40+ more] Error: Not a GitHub URL. Exited with code exit status 1 ``` ### Changes - `.circleci/config.yml` — bump `publish-docs: infinitered/publish-docs@0.4` → `@0.5`. ### Notes - Fix is upstream in [infinitered/orb-publish-docs#40](infinitered/orb-publish-docs#40), released as `v0.5.1` today. Replaces the unsafe `echo "export VAR=\"$VAL\""` patterns with `printf 'export VAR=%q\n' "$VAL"` in 5 internal scripts. - The `0.4 → 0.5` diff is internal only — no job, command, or parameter signatures change. All existing usage (`publish-docs/build_docs` and `publish-docs/publish_docs` with `ir_docs_config` params) remains compatible. - Verified `npx nx affected --target=version --base=origin/master --head=HEAD` returns 0 projects, so this merge will not cascade-trigger any unintended package releases. - Using `@0.5` (auto-resolves to latest 0.5.x) rather than pinned `@0.5.1` so future patch fixes apply automatically. Matches the prior `@0.4` style. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> infinitered/reactotron#1610
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.
Please verify the following:
yarn build-and-test:localpassesREADME.md(or relevant documentation) has been updated with your changesDescribe your PR
Bumps the
infinitered/publish-docsorb from@0.4(resolves to v0.4.13) to@0.5(resolves to v0.5.1). This unbreakspublish-docs/publish_docson master pushes when the merge commit body contains markdown / multi-line content.Why
The orb's v0.4.13 wrote unescaped multi-line shell content to
$BASH_ENVviaecho "export VAR=\"$VAL\"". When the merge commit's body had colons (e.g. inline JSON snippets) or newlines, bash interpreted each line as a command after sourcing$BASH_ENVat the start of the next step. Symptom on the master push for #1609:Changes
.circleci/config.yml— bumppublish-docs: infinitered/publish-docs@0.4→@0.5.Notes
v0.5.1today. Replaces the unsafeecho "export VAR=\"$VAL\""patterns withprintf 'export VAR=%q\n' "$VAL"in 5 internal scripts.0.4 → 0.5diff is internal only — no job, command, or parameter signatures change. All existing usage (publish-docs/build_docsandpublish-docs/publish_docswithir_docs_configparams) remains compatible.npx nx affected --target=version --base=origin/master --head=HEADreturns 0 projects, so this merge will not cascade-trigger any unintended package releases.@0.5(auto-resolves to latest 0.5.x) rather than pinned@0.5.1so future patch fixes apply automatically. Matches the prior@0.4style.🤖 Generated with Claude Code