Preserve starter publication timestamps on restart - #13
Merged
Conversation
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
1 participant
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.
Starting a PaperTrade replica upserted every built-in library publication with
published_at = now(). Adding a replica or rebooting a node therefore changed catalog order, sitemap metadata, and publication dates even when the seeded content was already complete.The conflict update now preserves both
published_atandupdated_at. New starter records still get a publication time on insert, and records that actually need content processing still get a publication time after processing.Validation: TypeScript client/server typecheck, server lint, and starter-work tests all pass.