How to Use GitHub release history in VS Code
Fetch published releases with tags, notes, dates, and assets, including prereleases. Use the history to compare upgrade paths; Git tags without an associated release are absent.
Prompts to try with GitHub release history in VS Code
Copy an example into VS Code, or ask in your own words.
Use GitHub release history to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from GitHub release history and tell me what changed since last week.
Check GitHub release history and summarize what you find in three bullet points.
Pull the newest data from GitHub release history and give me the result as a table.
Check GitHub release history every morning and tell me only when something changed.
How to set up GitHub release history in VS Code
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the hosted server
Use Add to VS Code on the console's Agents & MCP page, or run:
code --add-mcp '{"name":"spiral","type":"http","url":"https://api.spiral.ai/mcp"}' - Sign in
VS Code asks you to sign in when it first starts the server: sign in to Spiral and click Authorize. No API key. Run MCP: List Servers from the Command Palette to check that Spiral is running.
Use the Spiral skill
- Send VS Code this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run GitHub release history
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "github-com/repositories/releases", "input": { "repo": "<repo>" } }'
Then paste one of the prompts above: VS Code finds GitHub release history on Spiral, shows the price and runs it.
GitHub release history providers and prices
Spiral runs GitHub release history through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask VS Code for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Page | 1 to 1000 | 1 | 1-based page; has_next in the response says whether page+1 exists. |
| Per page | 1 to 100 | 30 | Records per page. |
Every API field of GitHub · Releases is on its tool page: open its card above.
What can you do with GitHub release history in VS Code?
Build a dependency review beside the code using GitHub files, release notes, issue evidence, and package advisories. A coding agent can compare those records with the project's manifests and turn the findings into proposed changes.
Review a dependency before adoption
Build an adoption brief covering repository status, contribution concentration, license text, issue categories and totals, release history, and reported vulnerability or malware concerns for the exact packages under consideration.
Prepare a dependency upgrade review
Compare the installed version with published releases, read migration files and known issue reports, and check relevant advisories. Include project status and contribution concentration when deciding how much upstream support to expect.
Investigate a reported package incident
Read the advisory and affected package ranges, compare release notes and manifests, then inspect related issue categories, reports, and totals. Keep a documented vulnerability fix separate from a malicious-package report.
Maintain a package security watch
Check a defined package list for malware reports and known advisory changes, then compare repository status, manifests, and published releases with the previous review. Produce a change report with links to the supporting records.
Assess upstream maintenance
Compare archive status, contribution concentration, release dates, issue categories, and backlog totals across candidate repositories. Read representative issue reports to explain the numbers.
Compare migration destinations
Compare two public projects using their README files, repository metadata, contribution distribution, release notes, and issue evidence. Summarize which documented limitations matter for the planned migration.
Write a vulnerability remediation brief
Explain a known CVE using its affected ranges, upstream files, and release notes. Check malicious-package reports separately and identify whether the evidence supports an upgrade or removing the package.
More on GitHub release history and VS Code
Overview
GitHub release history in other agents
Questions about GitHub release history in VS Code
Can VS Code use GitHub release history?
Yes. Add Spiral to VS Code as an MCP server, and VS Code can find and run GitHub release history like any built-in tool.
How much does GitHub release history cost in VS Code?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your VS Code plan is separate.
Do I need an Alexandria account to use GitHub release history in VS Code?
No. Spiral runs GitHub release history on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up GitHub release history in VS Code?
About two minutes: add the hosted server, then sign in.
Does VS Code wait while GitHub release history runs?
GitHub release history runs in the background. VS Code starts the run, checks on it and gives you the json when it's ready.
Can I reuse anything that is public on GitHub?
Public visibility alone does not grant unrestricted reuse. GitHub says that without a license, default copyright restrictions apply to source code; its Advisory Database has a separate CC BY 4.0 license.
How current is GitHub's data?
Freshness depends on the record. Contributor results can be a few hours old because GitHub caches them, while a file selected by branch can change whenever new commits arrive.
Does a GitHub release history include every version tag?
No. GitHub excludes Git tags that have no associated release, and its latest-release lookup excludes prereleases and drafts.
Do GitHub issues include pull requests?
GitHub's underlying issue responses can contain both, with pull requests identified separately. An issue-only backlog should exclude pull requests before its totals are compared.
Where do GitHub's malware reports come from?
GitHub automatically publishes malware advisories from the npm security team and the OpenSSF Malicious Packages repository. These reports concern malicious packages and are separate from ordinary vulnerability advisories.
Start using GitHub release history in VS Code
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into VS Code:
set up https://spiral.ai/SKILL.md


