ci: auto-sync install scripts to their dedicated S3 bucket - #1214
Merged
Conversation
plannotator.ai serves /install.sh, /install.ps1, and /install.cmd from the plannotator-install-scripts bucket, not the marketing bucket the deploy workflow syncs. Nothing in CI wrote to that bucket, so the served scripts went stale between hand syncs: v0.26.0 shipped while the site still served the July 31 installer, missing --skip-skills, the checkout guard, and the PowerShell < 7.2 fix. This adds a deploy-install-scripts job triggered by changes to the three scripts (plus a workflow_dispatch target), uploading them with content types and invalidating exactly those paths.
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.
TLDR: plannotator.ai serves the install scripts from the dedicated
plannotator-install-scriptsbucket, but no workflow ever wrote to it, so the live scripts went stale between manual syncs. v0.26.0 shipped while the site still served the July 31 installer (no--skip-skills, no checkout guard, and Windows users still hit the PowerShell < 7.2 bug the release notes said was fixed). The bucket was hand-synced today as the immediate fix; this PR makes the sync automatic.New
deploy-install-scriptsjob in deploy.yml: triggers on changes toscripts/install.{sh,ps1,cmd}(and a newinstall-scriptsworkflow_dispatch target), uploads the three scripts with content types, and invalidates exactly those CloudFront paths. Same OIDC role and environment as the marketing deploy. Verified end to end today: after the manual bucket sync, a sandboxedcurl -fsSL https://plannotator.ai/install.sh | bashinstalled v0.26.0 cleanly.AI-assisted.