Repository navigation
fix(domain): list only a release's own versions in its series - #675
Merged
Merged
Conversation
A release file made a draft kept its own series as the file stated it, with every version the series listed and what the file stated of each, and kept the version the file followed, with what the file stated of it. No Studio screen shows a series' versions, so publishing the draft put them in the creator's release unseen, where learners read them, with their notes, as earlier or later versions of the creator's series. Each next version carried them on, and one stated at the address of the next version kept that version from being published there. A file's own series now lists no version but the release, as a first import starts a series of the creator's own, and keeps a first version when the file describes the series. Nor does the release follow a version, as the one the file follows is not the creator's, so with nothing to compare it with, all of the draft is new. A release made a draft as the base of its next version keeps in its series only the release, the version it follows and the earlier versions in its folder. The next version copies only those earlier versions from an index too. Whichever folder the release is in, the draft keeps nothing stated of its default place in the instance, or of a later version there, where it and its next versions are published. What only a dropped statement led to is dropped with it. Refs: GHSA-jp29-vf56-5g4g
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
A release file made a draft kept its own series as the file stated it, with every version listed and what the file said of each, and kept the version the file followed. No Studio screen shows a series' versions, so publishing put them into the creator's release unseen, where learners read them as versions of the creator's series. Each next version carried them on, and one could keep the next version from being published at its default address.
docs/studio.mdanddocs/deck-library.mddescribe what an import and a next version keep.Refs: GHSA-jp29-vf56-5g4g