Artwork for the Connected Web website, including images and profile materials.
This repository now publishes @connected-web/assets to GitHub Packages for reuse in Connected Web tools.
Use this process for @connected-web/assets releases.
- Preferred path: create a GitHub Release tag (
vX.Y.Z) and letPublish Packages Releasepublish the npm package. - Do not manually rerun the release publish job for the same version after the GitHub Release is published, or npm publish will fail because the version already exists.
- Ensure PR checks are green.
- Merge the PR to
main.
For the first release there will be no previous tag. For later releases:
PREV_TAG=$(gh release list --limit 1 --json tagName --jq '.[0].tagName')
echo "Previous release: ${PREV_TAG}"
gh release view "${PREV_TAG}" --json publishedAtReview merged PRs and commits that will ship:
gh pr list --state merged --base main --limit 20
git log --oneline --decorate -20Use a file so release notes render cleanly.
Example:
cat > /tmp/release-notes-v0.1.0.md <<'EOF_NOTES'
Published packages:
- @connected-web/[email protected]
Highlights:
- Add publishable Connected Web asset package for GitHub Packages
- Generate `32`, `64`, `128`, `256`, `512`, and `large` logo variants
- Add PR and release workflows plus consumer smoke-test harness
EOF_NOTESgh release create v0.1.0 \
--target main \
--title "v0.1.0" \
--notes-file /tmp/release-notes-v0.1.0.mdThis triggers .github/workflows/publish-packages-release.yml.
gh run list --workflow publish-packages-release.yml --limit 1
gh run watch <run-id>npm view @connected-web/[email protected] version --registry=https://npm.pkg.github.comsource ~/.nvm/nvm.sh
export DEV_VERSION=0.1.0
export CONNECTED_WEB_PACKAGES_TOKEN=<github-packages-token>
./scripts/assets/run-consumer-smoke.sh