Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release version 0.10.0 #102

Merged
merged 33 commits into from
Aug 12, 2024
Merged

Release version 0.10.0 #102

merged 33 commits into from
Aug 12, 2024

Conversation

GaryJones
Copy link
Contributor

@GaryJones GaryJones commented Aug 9, 2024

I'll wait until Monday to merge, tag, and release.

pkevan and others added 30 commits March 2, 2018 16:54
By default, jquery UI has a 300ms timeout, by increasing it to 600ms it reduces the potential to flood the server with requests.
1. Remove stray spaces
2. Deduplicate blank lines
3. Obey EditorConfig including tabs vs. spaces and line end characters
4. Don't export development files
5. Add LICENSE file

Co-authored-by: Gary Jones <github@garyjones.io>
Without this, each CI job actually uses the latest version of WP, regardless of the version named in the job title.
With the later versions of Ubuntu that the CI jobs run on, comes newer versions of MySQL, which means this change is needed.

Once PHP 7.3 support is removed, this workaround can also be removed.
- Move screenshots to subdirectory for later easier deployment to WordPress.org plugin repository.
- Consolidate information from `readme.txt` into `README.md`, and remove `readme.txt` file.
- Move changelog content into a new `CHANGELOG.md` file.
Adds scripts to make it easier to bump the version numbers in various places. e.g. `npm run bump:minor`.
These development files are then not included when doing a release archive from GitHub, or a Composer pull down with `--prefer-dist`. Keep it to production-critical files (and a readme) only.
When pushing to WordPress.org SVN plugin repository, no development files are needed there (they aren't needed in production when someone grabs the plugin from WordPress.org) - these should be kept on the GitHub repo for developers.
This action, with the saved repository secrets, allows the pushing of a new GitHub release to WordPress.org automatically.
GaryJones and others added 3 commits August 9, 2024 16:12
@GaryJones GaryJones added this to the 0.10.0 milestone Aug 9, 2024
@GaryJones GaryJones self-assigned this Aug 9, 2024
@GaryJones GaryJones merged commit d9aa930 into main Aug 12, 2024
6 checks passed
@GaryJones GaryJones deleted the release/0.10.0 branch August 12, 2024 11:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants