Is your enhancement related to a problem? Please describe.
Release ads.txt version 1.4.1:
[x] Branch: Starting from develop, cut a release branch named release/X.Y.Z for your changes.
[x] Version bump: Bump the version number in ads-txt.php and readme.txt if it does not already reflect the version being released.
[x] Changelog: Add/update the changelog in both readme.txt and CHANGELOG.md
[x] Credits: Update CREDITS.md to include new contributors.
[x] New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .gitattributes.
[x] Readme updates: Make any other readme changes as necessary. CHANGELOG.md and README.md are geared toward GitHub and readme.txt contains WordPress.org-specific content. The two are slightly different.
[x] Merge: Make a non-fast-forward merge from develop to trunk (git checkout trunk && git merge --no-ff develop).
[x] Release: Create a new release, naming the tag and the release with the new version number, and targeting the trunk branch. Paste the changelog from CHANGELOG.md into the body of the release and include a link to the closed issues on the milestone (e.g. https://github.com/10up/ads-txt/milestone/1?closed=1).
[x] SVN: Wait for the GitHub Action to finish deploying to the WordPress.org repository. If all goes well, users with SVN commit access for that plugin will receive an emailed diff of changes.
[x] Close milestone: Edit the X.Y.Z milestone with release date (in the Due date (optional) field) and link to GitHub release (in the Description field), then close the milestone.
[x] Punt incomplete items: If any open issues or PRs which were milestoned for X.Y.Z do not make it into the release, update their milestone to X.Y.Z+1, X.Y+1.0, X+1.0.0 or Future Release.
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Is your enhancement related to a problem? Please describe.
Release ads.txt version 1.4.1:
release/X.Y.Zfor your changes.ads-txt.phpandreadme.txtif it does not already reflect the version being released.readme.txtandCHANGELOG.mdCREDITS.mdto include new contributors..gitattributes.CHANGELOG.mdandREADME.mdare geared toward GitHub andreadme.txtcontains WordPress.org-specific content. The two are slightly different.developtotrunk(git checkout trunk && git merge --no-ff develop).trunkbranch. Paste the changelog fromCHANGELOG.mdinto the body of the release and include a link to the closed issues on the milestone (e.g. https://github.com/10up/ads-txt/milestone/1?closed=1).Due date (optional)field) and link to GitHub release (in theDescriptionfield), then close the milestone.X.Y.Zdo not make it into the release, update their milestone toX.Y.Z+1,X.Y+1.0,X+1.0.0orFuture Release.Designs
No response
Describe alternatives you've considered
No response
Code of Conduct