Automate GitHub release asset publishing for extension version bumps

[Copilot]

The repository documented manual install via a ZIP from GitHub Releases, but no releases/tags were being generated, so users had no downloadable extension artifact. This change makes release publication happen from normal versioned delivery flow instead of relying only on ad-hoc tagging.

• Release trigger coverage

  • Extended Release Extension workflow to run on main pushes when release-relevant files change (package.json, extension/manifest.json, workflow file), in addition to existing tag and manual triggers.
  • Kept workflow_dispatch support; version input is now optional.

• Deterministic release metadata

  • Release metadata now resolves from:
    1. pushed tag (v*) when present,
    2. manual version input when provided,
    3. otherwise extension/manifest.json version (normalized to vX.Y.Z).
  • Added hard check that package.json and extension/manifest.json versions match before publishing.

• Release publication behavior

  • Release creation now pins target_commitish to the triggering commit SHA.
  • Existing packaged ZIP + SHA256 assets behavior is preserved.

• Docs alignment

  • Updated README release section to reflect automatic release creation from version bumps on main, while retaining tag/manual paths.

on:
  push:
    branches: [main]
    tags: ['v*']
    paths:
      - package.json
      - extension/manifest.json
      - .github/workflows/release.yml

[paladini]

@copilot você consegue já executar o comando de publicar a release da v1.0.0 da extensão, com o ZIP da extensão e tudo mais? Além do código que você já fez, de fato publicar uma release com conteúdo e arquivo anexados.

[Copilot]

@copilot você consegue já executar o comando de publicar a release da v1.0.0 da extensão, com o ZIP da extensão e tudo mais? Além do código que você já fez, de fato publicar uma release com co...

Não consegui publicar daqui porque o token GitHub disponível nesta sessão está inválido para ações de escrita/release. A automação ficou pronta no commit 2b7fbd9. Para publicar a v1.0.0 agora, rode no repositório: gh workflow run release.yml -R paladini/vibe-code-detector -f version=v1.0.0 (ou pela UI em Actions → Release Extension → Run workflow com v1.0.0).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/graphql
  • Triggering command: /usr/bin/gh gh auth status (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)