Add Modelplane v0.2 release announcement post#32
Merged
Conversation
Announce the v0.2 release with a short post covering the two new inference cluster providers (Nebius and Azure AKS), weighted request routing on ModelService, and cluster taints for reserving and draining capacity, with real manifests for each. Includes a cover image illustrating a weighted canary split. Marked draft so it renders on preview but stays out of production until we publish the announcement. Signed-off-by: Bassam Tabbara <bassam@upbound.io>
Each post carried its own copy of the author's photo under its blog bundle, so the same image was duplicated across posts. Move the avatars to a shared public/authors/ directory and point every post's frontmatter at the shared path, so an author's photo is stored once and reused. Signed-off-by: Bassam Tabbara <bassam@upbound.io>
Drafts were meant to render on preview deployments, but isVisible only gated on NODE_ENV. Vercel runs `next build` with NODE_ENV=production for every deployment, so preview builds hid drafts along with production. Check VERCEL_ENV=preview so drafts render on preview deployments while staying hidden on the production site. Signed-off-by: Bassam Tabbara <bassam@upbound.io>
Rework the opening to state the mission behind each release, retitle to "traffic you can direct", and correct the launch provider set: Modelplane provisioned on GKE and EKS at launch, not GKE alone. Signed-off-by: Bassam Tabbara <bassam@upbound.io>
bassam
marked this pull request as ready for review
July 16, 2026 20:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Announce the Modelplane v0.2 release with a short blog post. It covers the two new
inference cluster providers (Nebius and Azure AKS), weighted request routing on
ModelService, and cluster taints for reserving and draining capacity, each with areal manifest. Adds a cover image illustrating a weighted canary split.
Also consolidates author avatars: each post used to carry its own copy of the author's
photo under its blog bundle, duplicating the same image. This moves them to a shared
public/authors/directory and points every post at the shared path, so an author'sphoto is stored once. This touches the two existing posts'
avatarfrontmatter as well.Also fixes draft visibility on preview deployments.
isVisibleonly gated onNODE_ENV, but Vercel builds every deployment (preview included) withNODE_ENV=production, so preview hid drafts along with production, and this draft postdid not appear. It now also checks
VERCEL_ENV=preview, so drafts render on previewdeployments while staying hidden on the production site (verified with local builds
under both
VERCEL_ENV=previewandVERCEL_ENV=production).Checklist
andnpm run lintnpm run buildlocally.next lintonly offers to create an ESLint config (none exists in the repo yet), so there is nothing to run;npm run buildpasses. This change is content-only (MDX + images).npm run validate-posts(changed blog content) — passes.git commit -s.