Repository navigation
Bring AI asset generation to main for the next release - #2
Merged
Merged
Conversation
Taken as two files from main. Merging main into dev would delete MAINTAINING.md, which main does not carry on purpose.
Generate AI images, video and audio from a prompt
# Conflicts: # MAINTAINING.md
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.
Bring AI asset generation to main for the next release
Only a tag on
mainpublishes, so the Generation resource merged intodevin #1 has to reachmainbefore it can ship.This is
devmerged intomainwithMAINTAINING.mdremoved, since that guide stays ondev. The tree isdev's minus that file, so nothing here needs review beyond #1.package-lock.jsondrops a stale@shotstack/clientry thatpackage.jsonno longer declares. The lockfile now matchesdev's.The version stays 0.1.1. After merge,
npm run releasebumps it: tag0.2.0-rc.1first and scan it, since the community-package scan only reads published versions, then tag0.2.0.Verify:
git diff origin/dev origin/release/ai-generation --statlists onlyMAINTAINING.md.GITHUB_BASE_REF=main node scripts/review-check.mjspasses 40/40 with 86 tests.Risk: merging publishes nothing; only a tag does. Until a tag, rollback is a revert.