Update/repo org #1
Merged
Conversation
This file contains 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
8 tasks
* main: minor composer dependency updates update plugin version to 3.15.7 also include npm i to update package lock file with new version alpha order command add cleanup, build and i18n to npm command too update plugin file in version bump script too update package.json version with a script NPM Dev(deps-dev): Bump cypress from 13.16.0 to 13.16.1 NPM(deps): Bump @heroicons/react from 2.1.5 to 2.2.0 NPM Dev(deps-dev): Bump tailwindcss from 3.4.15 to 3.4.16 NPM(deps): Bump @wordpress/i18n from 5.12.0 to 5.13.0 NPM(deps): Bump react-router-dom from 6.28.0 to 7.0.2 # Conflicts: # bluehost-wordpress-plugin.php # composer.lock # package-lock.json # package.json
|
Some tests are failing and I've found that it is because in the test env the plugin slug matches the repo (wp-plugin-bluehost) and is not the same as when using the build (bluehost-wordpress-plugin) in an actual env. Thus the plugin uninstall commands were uninstalling our plugin during tests and then all following tests failed (for good reason). The modules uninstalling plugins are coming soon and e-commerce and I have created PRs to update those commands to specifically uninstall the plugins that the test installed rather than every plugin with an exclude list.
Once those are merged I can tag releases and update the modules in this PR (and remove the skipped tests) and then all tests should pass. |
* main: Update description to mention PR due date is a week before run npm audit fix npm run set-version-bump - Version updated 3.15.7 => 3.15.8 update solutions module and solutions test exclusion Add IDs to settings sections NPM(deps): Bump @reduxjs/toolkit from 2.4.0 to 2.5.0 Composer(deps): Bump newfold-labs/wp-module-patterns from 2.8.0 to 2.8.1 NPM Dev(deps-dev): Bump @wordpress/eslint-plugin from 21.6.0 to 22.0.0 NPM(deps): Bump @wordpress/dom-ready from 4.13.0 to 4.14.0 NPM(deps): Bump react-use from 17.5.1 to 17.6.0 Fix 'isJarvis' check that always returned true Composer(deps): Bump newfold-labs/wp-module-data from 2.6.7 to 2.6.8 # Conflicts: # bluehost-wordpress-plugin.php # composer.json # composer.lock # languages/wp-plugin-bluehost.pot # package-lock.json # package.json
wpscholar
approved these changes
Dec 20, 2024
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.
Proposed changes
This is in preparation of migrating the bluehost repo to newfold-labs.
bluehost-wordpress-pluginfolder name rather than the repo name.See https://jira.newfold.com/browse/PRESS10-41 for the full plan.
Type of Change
Production
Development
Video
Checklist
Further comments