WP Manifestindependent plugin directory
manifest / seo / novastream-seo

Novastream SEO

Custom SEO WordPress Plugin

by NovaStream · github.com/novastreamca/novastream-seo · website

0stars
0forks

Install

No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:

wp plugin install https://github.com/novastreamca/novastream-seo/archive/refs/heads/main.zip

Declares an update source (https://github.com/NovaStreamCA/novastream-seo), so updates arrive through the plugin's own updater.

Readme

NovaStream SEO

NovaStream's WordPress SEO plugin.

Requirements

  • WordPress 6.5 or newer is recommended for native plugin-dependency handling.
  • Advanced Custom Fields Pro must be installed and active separately.

ACF Pro is intentionally not bundled with this plugin. WordPress can enforce the dependency when ACF Pro uses its standard advanced-custom-fields-pro plugin directory. A runtime check also prevents fatal errors and displays an administrator notice on older or manually managed installations.

Updates and releases

The plugin uses Plugin Update Checker 5.7 to follow stable, non-prerelease GitHub releases and tags. Commits on main are not a production release by themselves. Do not add a GitHub token, deploy key, or other credential to the plugin: every file shipped with a WordPress plugin must be treated as public.

To publish a release:

  1. Update both version declarations in seo.php.
  2. Merge the release commit into main.
  3. Create a matching Git tag and GitHub release (for example, 1.1.9).
  4. Verify the update from a WordPress installation before broad deployment.

The repository must remain public for credential-free update checks and downloads to work on installed sites.

The updater is vendored at vendor/plugin-update-checker. When upgrading it, copy the official runtime package and retain its MIT license.txt; do not copy examples, build scripts, or development configuration into this plugin.

Security

Never commit credentials, even when the repository is private or the value is encoded. If a credential is committed, revoke it first and then remove it from all branches and tags before making the repository public.

Read the full README on GitHub →

Releases

TagPublished
1.2.1 Aug 18, 2026
1.2.0 Aug 18, 2026
1.1.9 Aug 18, 2026
1.1.7 Jul 27, 2026
1.1.6 Jul 27, 2026
1.1.5 Nov 21, 2025
1.1.4 Apr 17, 2025
1.1.3 Dec 18, 2024
1.1.2 Dec 10, 2024
1.1.1 Dec 10, 2024
1.1.0 Sep 6, 2022
1.0.6 Aug 26, 2022
1.0.5 Aug 26, 2022
1.0.4 Aug 26, 2022
1.0.3 Aug 25, 2022
1.0.2 Aug 24, 2022
1.0.1 Aug 5, 2022

These releases are tags only. The author does not attach a packaged zip, so there are no download counts to report.