feat(cdn): add versioned artifact endpoints

[adambenhassen]

Description

Add support for retrieving CDN artifacts by version ID.

New endpoints

• GET /artifacts/v1/:targetId/version/:versionId/:artifactType
• GET /artifacts/v1/:targetId/version/:versionId/contracts/:contractName/:artifactType

Artifacts are now written to both the latest path and a versioned path during schema publish, enabling retrieval of historical versions.

Closes #7222
Closes #7156

[gemini-code-assist]

Summary of Changes

Hello @adambenhassen, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the CDN's capabilities by enabling the retrieval of schema artifacts based on their version ID. Previously, only the latest version was directly accessible. Now, when a schema is published, its artifacts are stored in a way that allows both the current "latest" version and any specific historical version to be fetched via dedicated CDN endpoints. This provides users with the ability to inspect or roll back to previous schema definitions, improving schema management and debugging workflows.

Highlights

• Versioned CDN Endpoints: Introduced new API endpoints to retrieve schema artifacts by a specific version ID, allowing access to historical schema states.
• Dual Artifact Storage: During schema publication, artifacts are now stored in both a "latest" path and a version-specific path, ensuring that historical versions are preserved and retrievable.
• Comprehensive Integration Tests: Added extensive integration tests to validate the functionality of the new versioned CDN endpoints, covering successful retrieval, handling of non-existent or invalid version IDs, and authentication scenarios.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package	Version	Info
hive	8.13.0-alpha-20251209212135-59ec6e10f5bcf548c7a448f22a479ae5ce79b621	npm ↗︎ unpkg ↗︎

[github-actions]

📚 Storybook Deployment

The latest changes are available as preview in: https://pr-7348.hive-storybook.pages.dev

[gemini-code-assist]

Code Review

The pull request introduces support for versioned CDN artifacts, allowing retrieval of historical schema versions. The changes include new API endpoints, modifications to the artifact storage writer to handle versioned keys, and updates to schema publishing and deletion logic to pass version IDs. Comprehensive integration tests have been added to validate the new functionality, covering various scenarios including successful retrieval, handling of non-existent or invalid version IDs, and authentication. The implementation demonstrates good practices such as Zod for input validation, detailed logging, and appropriate cache control for immutable versioned artifacts. The logic for writing versioned artifacts before updating the 'latest' ensures data consistency in case of partial failures.

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://pr-7348.hive-landing-page.pages.dev

[github-actions]

🐋 This PR was built and pushed to the following Docker images:

Targets: build

Platforms: linux/amd64

Image Tag: 59ec6e10f5bcf548c7a448f22a479ae5ce79b621

[n1ru4l]

This could also mention the availability of the new header x-hive-schema-version-id.

[n1ru4l]

Looking good! 🥳 Only one minor comment for the changeset: https://github.com/graphql-hive/console/pull/7348/files#r2598287101

After merging this, please follow up with a PR for a product update and also updating existing documentation for the CDN