Promote dev to master: MinIO quay.io images + SEO/landing batch - #424
Merged
Merged
Conversation
…allow-list, md-twin alternates, HSTS + cf-visitor https redirect
…work pages, home and top storage guides
… decorative scene
…oviders, Node version, privacy and README
…and analytics on demand
…ts in the docs link gate
…Hub's minio repos are gone
ci(minio): pull the pinned MinIO images from quay.io now that Docker Hub's minio repos are gone
seo(landing): serve the IndexNow key file
docs(landing): claim-integrity pass — truthful wording for parity, providers, Node version, privacy and README
seo(landing): query-driven titles, H1s and descriptions for the framework pages, home and top storage guides
Resolves the HomepageHero conflict with #417 (query-driven H1 copy). Kept #419's structure - a plain <h1> with RisingWords and a plain closing <div> for the CTA row - because #419 deliberately removes framer-motion from the LCP path. That side is also the only compilable one: #419 deleted both the headingVariants definition and the BlurText import, and those deletions merged cleanly, so dev's motion.h1/BlurText branch would reference two symbols that no longer exist in this file. Carried #417's contributions into that structure: - the query-driven heading copy, now fed to RisingWords instead of BlurText (fw ? `${fw.name} File Uploader` : 'Open-Source File Uploader') - the framework-only quickstart Link in the CTA row, which #417 wrote without a motion wrapper precisely so it would survive this merge
seo(landing): Organization/WebSite entity JSON-LD, AI-crawler robots allow-list, md-twin alternates, HSTS + cf-visitor https redirect
perf(landing): fix mobile LCP and cut the marketing pages from 6.3 MB to 0.6 MB
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
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
2 participants
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 this promotes
Seven PRs merged to dev on 2026-09-16, all authored by @BSalaeddin:
minio/minioandminio/mcon 2026-09-12. Same two digests; this is what turns the cross-framework E2E job green again on master-targeted PRs.Merge note on #419
#419 and #417 both rewrote the hero heading in
apps/landing/src/components/HomepageHero/index.tsx. Resolved in 409c9c7 by keeping #419's motion-free structure (plain<h1>+RisingWords, plain CTA<div>) and carrying #417's query-driven copy and framework-quickstart Link into it. That was the only compilable resolution: #419 had deletedheadingVariantsand theBlurTextimport, and both deletions merged cleanly. Passed all 18 checks on the PR before merge.Release impact
None. No changesets in this batch —
.changeset/stays empty, sopublish.ymlwill not open a Version Packages PR or publish anything. All changes are inapps/landing,docker-compose.yml, CI workflows,.gitignoreandCLAUDE.md.Follow-ups after this lands