Repository navigation
chore(release): 0.7.0 - #59
Merged
Merged
Conversation
…pload step; phpcs reasons on the export queries
…s before payment, privacy text names usernames and every comment status
Member
Author
|
ork2 read-review @3804424: OK, no MUST.
|
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
Release prep for Contentrain Bridge 0.7.0, built on t3's prep branch
chore/release-0.7.0@372ad1c(merged, no rebase; it keeps t3's phpcs reasons, the RELEASING Plugin Check section and the WP.org upload step), with bridge main440aa52merged in (#57 robots switch, #58/counts).CONTENTRAIN_BRIDGE_VERSIONandStable tag(package.jsoncarries no version). The metadata check passes locally:0.7.0 0.7.0 0.7.0./counts: published entries per content type plus media files, so Migrate can price before payment. It sends numbers only, needs the same sign-in as an export, and is never public.exporter.php:45,100,models.php:335).jobs.phpcomment batch: nocomment_approvedfilter). The comments FAQ says the same.Gate (the RELEASING sequence, own Docker project
t8rel, port 8195, started fromdown -v, load < 40)npm ci --ignore-scripts: oktest:wordpress(KEEP=1): 394 checks passedtest:plugin(Plugin Check 2.1.0): 0 errors / 4 warnings, allPrefixAllGlobals.NonPrefixedHooknameFound(the four WPML hook names). This is the expected number: nophpcs:ignoreline moved in the merge with feat(robots): the owner can let Contentrain Migrate read the site through robots.txt #57/feat(remote): GET /counts — WordPress's published counts per type and media, for a price before payment; /about names the capability #58.test:store:contentrain validate14 models / 62 entries · canonical byte parity 55 files · 5 documents with frontmatternpm test: 13/13 ·test:reader: every escape-bearing value survivespackage: 33 files, header and constant 0.7.0 inside the zip; local sha2564ea11436…a750(the release asset is built by CI, so its sha is the one to record)ORK tags
v0.7.0after the review and CI pass, then uploads to WP.org (RELEASING § WordPress.org).