Inttegro demos 1.1.0
·
11 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
[!IMPORTANT]
This release is preserved for permalink integrity and is superseded by v1.1.1, which fixes deployment-ref preparation.
Inttegro demos 1.1.0
This release turns the demo suite into a reader-owned deployment experience.
Highlights
- Publishes a polished catalogue for the
demos.inttegro.devhome. - Adds release-aware deployment metadata and active
{framework}-demo.inttegro.devhostnames while keeping reader manifests
host-neutral. - Prepares Cloudflare Workers deployments for Next.js, Nuxt, and Express.
- Prepares framework-native Vercel deployments for Next.js and Nuxt.
- Adds container, Render Blueprint, and Railway configuration for Express,
Django, FastAPI, Rails, Laravel, Go, and Spring Boot. - Documents provider trade-offs, environment contracts, verification gates,
and immutable generated deployment refs for humans and machine readers. - Records the current Python Workers transport incompatibility and Java SDK
publication gate rather than presenting non-working deploy buttons.
Release safety
Deploy buttons request the reader's own Inttegro test key. No credential or
provider secret is embedded in source, query parameters, generated catalogue
metadata, or release files. Render examples disable automatic upstream deploys;
generated deployment refs are versioned and immutable.
The inttegro.dev domain is active on Cloudflare. Inttegro-owned custom hosts
are attached during release deployment and are deliberately absent from the
configurations cloned by readers.