release-mac.sh's get_token() couldn't read tea's OAuth token (stored encrypted in the keychain, not config.yml), so it fell back to a stale git-credential token and 401'd on upload. Replaces the curl+token upload with tea release create / tea releases assets create, which carry and refresh the OAuth token automatically. Also adds a docs-coverage assertion that landing.js platform download links point at the current version.
release-mac.sh's get_token() couldn't read tea's OAuth token (stored encrypted in the keychain, not config.yml), so it fell back to a stale git-credential token and 401'd on upload. Replaces the curl+token upload with `tea release create` / `tea releases assets create`, which carry and refresh the OAuth token automatically. Also adds a docs-coverage assertion that landing.js platform download links point at the current version.
release-mac.sh get_token() could not read tea's OAuth token (stored
encrypted in the keychain, not config.yml), so it fell back to a stale
git-credential token and 401'd on upload. Replace the curl+token upload
with `tea release create` / `tea releases assets create`, which carry
and refresh the OAuth token automatically.
Add a docs-coverage assertion that landing.js platform download links
point at the current version, so the manual version bump cannot drift.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
release-mac.sh's get_token() couldn't read tea's OAuth token (stored encrypted in the keychain, not config.yml), so it fell back to a stale git-credential token and 401'd on upload. Replaces the curl+token upload with
tea release create/tea releases assets create, which carry and refresh the OAuth token automatically. Also adds a docs-coverage assertion that landing.js platform download links point at the current version.