Repository navigation
Conversation
The builds list and the build details, size analysis download, comparisons, compare and compare download endpoints hid an artifact once it was older than the organization's current Size Analysis retention. A plan change therefore changed which existing builds could be read. They now compare the date_size_analysis_expires stamped on the artifact at creation. An artifact without a stamped date keeps the previous behavior, so nothing appears or disappears while existing rows are being backfilled. The 90 day fallback for an unlimited retention is gone: such an artifact stays readable until cleanup deletes it by age. Endpoints that load the artifact through PreprodArtifactEndpoint now also return 404 once it is past date_expires. Refs EME-1314
This was referenced Nov 20, 2026
Contributor
decision-model-linterapi
decision-model-linter: 49 calls on 10 files, 112,363 input tokens, $0.0047, model typesafe/jev-1.13-20260917 |
Contributor
Sentry Snapshot Testing
|
Merge the stamping change: an artifact without a stamped date is one that predates the columns, and it always falls back to the current retention counted from date_added, as before the columns existed.
A build was hidden from the distribution list and its details returned 404 once its size analysis expired, although the build is kept for the Build Distribution retention, which is longer on the Team plan. It could then only be reached through its install link. The distribution list and the build details now show a build until date_expires and leave out its size analysis once that has expired. The size and snapshot lists and the size analysis endpoints still stop at the Size Analysis retention.
This branch has not been deployed
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.
The builds list and the size analysis endpoints hide a build once it is older than the organization's current Size Analysis retention, so a plan change also changes which existing builds can be read. They now compare the dates that were stamped on the artifact when it was created.
A build stays visible until it expires. Before, the distribution list and the build details also stopped at the Size Analysis retention. On the Team plan a build therefore disappeared after 30 days, although it is kept and can be installed for 13 months. The distribution list, its CSV export and the build details now show a build until
date_expires, and leave its size analysis out of the response oncedate_size_analysis_expireshas passed. The size and snapshot lists and the size analysis endpoints still stop at the Size Analysis retention. When this deploys, Team builds between 30 days and 13 months old come back in the distribution list, and the build details page shows its existing "No size analysis" state for them.Rows without a date. For an artifact without a stamped date, the size analysis keeps the previous rule: the current retention, counted from
date_added. The backfill setsdate_addedplus the current retention, which is the same instant, so the backfill does not change what can be read, whether it runs before or after this deploys.Build Distribution had no retention check on read. Endpoints that load the artifact through
PreprodArtifactEndpoint, which include the install details and the download, now return 404 once the artifact is pastdate_expires. On the Developer plan both retentions are 30 days, sodate_expiresis 30 days after the upload and these endpoints stop serving a build then. Endpoints that load artifacts in another way are not changed here: the snapshot endpoints, check-for-updates, the latest build, and the public install details and size analysis endpoints.Refs EME-1314
Cross-repository landing order (top to bottom)
cleanuponce they are past their stamped expiry--daysstill does on the preprod artifacts cleanup cron