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

bug: Plugin updates not working #337

Closed
colinmurphy opened this issue Jan 30, 2025 · 3 comments · Fixed by #341
Closed

bug: Plugin updates not working #337

colinmurphy opened this issue Jan 30, 2025 · 3 comments · Fixed by #341
Assignees
Labels
type: bug Issue that causes incorrect or unexpected behavior

Comments

@colinmurphy
Copy link
Contributor

Issue

As reported by @justlevine you are not getting notified of new releases for this plugin.

How to replicate

If you have or download an older release of content blocks, you won't be notified in the WordPress plugin page that you need to update the plugin.

@colinmurphy colinmurphy added the type: bug Issue that causes incorrect or unexpected behavior label Jan 30, 2025
@colinmurphy colinmurphy self-assigned this Jan 30, 2025
@github-project-automation github-project-automation bot moved this to 🆕 Backlog in Headless OSS Jan 30, 2025
@colinmurphy colinmurphy moved this from 🆕 Backlog to 🔖 Ready for Development in Headless OSS Jan 30, 2025
@colinmurphy colinmurphy changed the title bug: Plugin update bug: Plugin updates not working Jan 30, 2025
@colinmurphy colinmurphy moved this from 🔖 Ready for Development to 🏗 In progress in Headless OSS Jan 30, 2025
@colinmurphy
Copy link
Contributor Author

This is in progress and we should have a fix in place next week.

colinmurphy added a commit that referenced this issue Feb 6, 2025
* Replaced old updater service with the new WPE Updater service. fixes  #337

* Fixed PHPStan issues

* PHPCS fixes
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Closed in Headless OSS Feb 6, 2025
@colinmurphy colinmurphy moved this from ✅ Closed to Merged ready to release in Headless OSS Feb 7, 2025
@josephfusco
Copy link
Member

@josephfusco josephfusco moved this from Merged ready to release to ✅ Closed in Headless OSS Feb 18, 2025
@justlevine
Copy link
Contributor

justlevine commented Feb 18, 2025

@josephfusco nope, its reproducable with both 4.8.0 and develop

Edit: Sorry, this got displayed to me as a reply to #350

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Issue that causes incorrect or unexpected behavior
Projects
Status: ✅ Closed
Development

Successfully merging a pull request may close this issue.

3 participants