Skip to content

Correct Workspace and storage products in hosting data - #99

Merged
ralyodio merged 1 commit into
mainfrom
bot-email/hosting-verification-20260913
Sep 13, 2026
Merged

ralyodio merged 1 commit into
mainfrom
bot-email/hosting-verification-20260913

Conversation

@ralyodio

Copy link
Copy Markdown
Contributor

The published Hosting database is already delivered with 1,400 items, but four Cap Connect Google Workspace products and four online-storage products are incorrectly labeled VPS. Recognize Google Workspace/G Suite as addons and the French stockage group as storage, using the existing classifier. Workspace seats then leave the plan feeds when the source refreshes; storage products retain their plan identity with the correct offer kind.

The attached verification report records the live source counts, six working API/RSS feeds, FindHost attribution, observed enrichment, and paused optional sources. Replaying all 552 public storefront records changes exactly these eight classifications and preserves every external ID. Two public raw product fixtures reproduce the error without network access.

Validation:

  • Regression fails before the correction and passes afterward.
  • 77 focused hosting, storefront, keyed-source, enrichment, and BuyVPS tests pass.
  • Full suite: 1,575 tests pass across 91 files.
  • Repository-wide Biome passes with existing warnings; git diff --check passes.
  • Public collection/source/item and all six feed API/RSS endpoints returned HTTP 200.

No migration, new dependency, production write, or source rerun. This change is not deployed: the eight live records still need deployment and the next ordinary storefront refresh. Credentialed and OpenServer sources remain paused.

@ralyodio
ralyodio marked this pull request as ready for review September 13, 2026 17:10
@ralyodio
ralyodio merged commit 3831505 into main Sep 13, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant