@omercnet/paseo-omp 1.2.0-next.214.1 → 1.2.0-next.215.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/package.json +1 -1
- package/server/package-version.ts +1 -1
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Community OMP integration for Paseo. The plugin registers the distinct `omp-plugin` provider plus named profile providers and coexists with Paseo's bundled `omp` provider.
|
|
4
4
|
|
|
5
|
-
> **
|
|
5
|
+
> **Stable:** see [Support](SUPPORT.md) for supported versions and known limitations, and review release notes for any migration requirements before upgrading.
|
|
6
6
|
|
|
7
7
|
## Demo
|
|
8
8
|
|
|
@@ -38,7 +38,7 @@ Open the **OMP** sidebar to review the provider-profile contract, choose which c
|
|
|
38
38
|
- [Compatibility, limitations, and support](SUPPORT.md)
|
|
39
39
|
- [Test matrix and release verification](TESTING.md)
|
|
40
40
|
- [Core-provider issue and parity audit](docs/core-provider-issue-audit.md)
|
|
41
|
-
- [
|
|
41
|
+
- [Release checklist](docs/release-checklist.md)
|
|
42
42
|
|
|
43
43
|
The plugin uses public Paseo 0.9 and 0.10 provider and client contracts and registers distinct `omp-plugin` and `omp-plugin-<profile>` identities; it does not modify the bundled `omp` provider.
|
|
44
44
|
|
package/package.json
CHANGED
|
@@ -1,2 +1,2 @@
|
|
|
1
1
|
/** Release Please keeps this bundle-safe constant aligned with package.json. */
|
|
2
|
-
export const PASEO_OMP_PACKAGE_VERSION = "1.2.0-next.
|
|
2
|
+
export const PASEO_OMP_PACKAGE_VERSION = "1.2.0-next.215.1"; // x-release-please-version
|