Repository navigation
chore(release): 1.1.0 (#25) - #26
Merged
Merged
Conversation
The GitHub Release zip shipped the WordPress.org listing assets (banners, icons and their HTML sources) inside the plugin, because zip.js never excluded them; .distignore did, so the SVN deploy was clean. The integrity check now fails the build if the folder leaks again. Refs #25 Co-Authored-By: Claude Opus 5.5 <[email protected]>
Stale since 1.0.0: 100 → 213 strings, picking up everything since #17 and the Settings → SMTP labels. Refs #25 Co-Authored-By: Claude Opus 5.5 <[email protected]>
Version header, MAILYARD_VERSION, readme Stable tag, package.json and the lockfile root go to 1.1.0; the 1.1.0 changelog entry gets its date. Closes #25 Co-Authored-By: Claude Opus 5.5 <[email protected]>
Closed
7 tasks
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.
Closes #25
What
Releases 1.1.0: the simple-SMTP rewrite (#17) and Settings → SMTP (#20). This bumps the version, dates the changelog, regenerates the POT, and stops the GitHub Release zip from carrying the WordPress.org listing assets.
Why
wordpress.org still serves 1.0.1.
mainhas carried the 1.1.0 changelog since #18. The header said 1.0.2, which was never tagged.How
mailyard.phpVersion:+MAILYARD_VERSION,readme.txtStable tag,package.jsonand the lockfile root → 1.1.0. The changelog entry is dated 2026/10/09.release.ymlchecks that the tag matches both the header and the Stable tag.languages/mailyard.potregenerated (100 → 213 strings; it was stale since 1.0.0).scripts/zip.jsnow excludes.wordpress.org/(banners, icons and their HTML sources were inside the 1.0.1 and 1.1.0 GitHub zips;.distignorealready kept them out of SVN). The integrity check fails if the folder leaks again. The zip is 65 files / 400 KB.assets.yml→ merge → tagv1.1.0→release.ymlpublishes the GitHub Release and deploys trunk +tags/1.1.0+ assets to SVN → re-enableassets.yml. That keeps trunk's readme from pointingStable tagat atags/1.1.0that doesn't exist yet.[skip actions]isn't used because it would likely also skip the tag-triggered release.Testing
npm run zip→mailyard-1.1.0.zip, integrity check passedadmin.php?page=mailyardredirects there; Dashboard/Plugins load;debug.logstays emptyofflinewith the Cc header keptmain(see Abilities REST: optional-input abilities reject a call with no input #23)Version bump approved by the user ("release").
🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.