Automated patch release: 4.4.1 #399
Conversation
Bumps [newfold-labs/wp-module-hosting](https://github.com/newfold-labs/wp-module-hosting) from 1.1.2 to 1.1.3. - [Release notes](https://github.com/newfold-labs/wp-module-hosting/releases) - [Commits](newfold-labs/wp-module-hosting@1.1.2...1.1.3) --- updated-dependencies: - dependency-name: newfold-labs/wp-module-hosting dependency-version: 1.1.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
- Add StagingRedirect component to redirect /staging to /wp-admin/admin.php?page=nfd-staging
…tools-blank-page add redirect for specific route
…/newfold-labs/wp-module-hosting-1.1.3 Composer(deps): Bump newfold-labs/wp-module-hosting from 1.1.2 to 1.1.3
Bumps [newfold-labs/wp-module-performance](https://github.com/newfold-labs/wp-module-performance) from 3.1.6 to 3.2.6. - [Release notes](https://github.com/newfold-labs/wp-module-performance/releases) - [Commits](newfold-labs/wp-module-performance@3.1.6...3.2.6) --- updated-dependencies: - dependency-name: newfold-labs/wp-module-performance dependency-version: 3.2.6 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…/newfold-labs/wp-module-performance-3.2.6 Composer(deps): Bump newfold-labs/wp-module-performance from 3.1.6 to 3.2.6
Bumps [newfold-labs/wp-module-onboarding](https://github.com/newfold-labs/wp-module-onboarding) from 3.0.1 to 3.0.2. - [Release notes](https://github.com/newfold-labs/wp-module-onboarding/releases) - [Commits](newfold-labs/wp-module-onboarding@3.0.1...3.0.2) --- updated-dependencies: - dependency-name: newfold-labs/wp-module-onboarding dependency-version: 3.0.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…/newfold-labs/wp-module-onboarding-3.0.2 Composer(deps): Bump newfold-labs/wp-module-onboarding from 3.0.1 to 3.0.2
Add more redirects for legacy paths
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Bumps [newfold-labs/wp-module-onboarding](https://github.com/newfold-labs/wp-module-onboarding) from 3.0.2 to 3.0.3. - [Release notes](https://github.com/newfold-labs/wp-module-onboarding/releases) - [Commits](newfold-labs/wp-module-onboarding@3.0.2...3.0.3) --- updated-dependencies: - dependency-name: newfold-labs/wp-module-onboarding dependency-version: 3.0.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…/newfold-labs/wp-module-onboarding-3.0.3 Composer(deps): Bump newfold-labs/wp-module-onboarding from 3.0.2 to 3.0.3
* develop: Composer(deps): Bump newfold-labs/wp-module-onboarding
…omment-for-build * update/workflow-triggers-and-concurrency: update release PR workflow triggers and concurrency
Add persistent PR comment with link to build
…d-concurrency update release PR workflow triggers and concurrency
* develop: yml linting update formatting again try with less indentation try another PR comment formatting lint whitespace fix and fix markdown update comment body with friendly fomatting use artifact action output for artifact link update comment link text add persistent PR comment with link to build update release PR workflow triggers and concurrency # Conflicts: # .github/workflows/upload-artifact-on-push.yml
Latest Plugin Build⬇️ Download build artifact: |
Took a while to make sense of this. I could see the file listed in the dist list here: https://github.com/newfold-labs/wp-plugin-bluehost/actions/runs/16270779442/job/45937588548#step:16:1045 but also, when I download the zip file I couldn't find the file either. It seems like the upload-artifact workflow was updated recently to ignore hidden files and our build on push workflow hasn't included the hidden staging file for a couple months. The goos news is that our release build workflow has continued to include this hidden file (since in that workflow we have a step that manually performs the zip, so the hidden file is included). This was just a fault in the build workflow on push, and the actual release has been working still. I got the build workflow updated today to use the |
There was a problem hiding this comment.
Not a big fan of skipping tests, especially since I had pinged about https://github.com/newfold-labs/wp-module-migration/releases/tag/1.5.7 a while back, it fixes the migration onboarding redirect test issue. We missed unskipping it last time. That said, it should be fine as long as we remember to uncomment it later.
There was a problem hiding this comment.
I also noticed that https://github.com/newfold-labs/wp-module-performance/releases/tag/3.2.8 hasn't been included. I had pinged about this too. It fixes a bug with link prefetching that was found in this release. Can we add it? @circlecube
|
@arunshenoy99 - We need to adhere to the release window to ensure quality and consistency. The module releases available when the release candidate is created are included in the release. While I appreciate that the module updates include useful bug fixes, unless they address a critical issue, they will be included in the next scheduled release (which is prepared immediately after this one is tagged). Following this window is important because it gives the QA team the time they need to thoroughly test. Ideally, no module updates should be included unless it was tagged before the release window closed. We've seen recent issues in releases that didn't have ample time for QA tests. |
Changes in this pull request
4.4.0to4.4.1Merged PRs since last release
Generated automatically by CI workflow (see prep-release workflow).