fullstackgtm 0.28.2 → 0.28.3
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/CHANGELOG.md +9 -0
- package/CONTRIBUTING.md +8 -8
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,15 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
|
5
5
|
and the project adheres to [Semantic Versioning](https://semver.org/).
|
|
6
6
|
The path to 1.0 is planned in [docs/roadmap-to-1.0.md](./docs/roadmap-to-1.0.md).
|
|
7
7
|
|
|
8
|
+
## [0.28.3] — 2026-06-16
|
|
9
|
+
|
|
10
|
+
Fix broken links in the published mirror. CONTRIBUTING.md and CLAUDE.md
|
|
11
|
+
referenced `../../docs/open-core-boundary.md` — a monorepo-root path that
|
|
12
|
+
escapes the repo on the mirror (where the package is the repo root) and targets
|
|
13
|
+
a doc the mirror doesn't carry. Made those references self-contained (the
|
|
14
|
+
open-core model and release ritual are explained inline). A full sweep confirms
|
|
15
|
+
every relative link in the shipped docs now resolves within the package/mirror.
|
|
16
|
+
|
|
8
17
|
## [0.28.2] — 2026-06-16
|
|
9
18
|
|
|
10
19
|
Collaborator/co-maintainer onboarding (from a readiness review). No runtime
|
package/CONTRIBUTING.md
CHANGED
|
@@ -16,11 +16,12 @@ github:fullstackgtm/core` works without a build step).
|
|
|
16
16
|
- **Issues / PRs:** open them on the public mirror (`fullstackgtm/core`). A
|
|
17
17
|
maintainer applies accepted changes in the monorepo with credit
|
|
18
18
|
(`Co-authored-by`); they land in the next mirrored release.
|
|
19
|
-
- The open/closed boundary
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
19
|
+
- The open/closed boundary: client tools, the canonical model, rules, the
|
|
20
|
+
plan/apply contract, connectors, CLI, and MCP server are open; the hosted Full
|
|
21
|
+
Stack GTM application's server code is not. **Features never move from open to
|
|
22
|
+
closed**, and new work here must run standalone (no hosted deployment
|
|
23
|
+
required). (Maintainers: the full boundary policy lives in
|
|
24
|
+
`docs/open-core-boundary.md` in the development monorepo.)
|
|
24
25
|
|
|
25
26
|
## Architecture
|
|
26
27
|
|
|
@@ -72,9 +73,8 @@ the spec) and run the security suite (`fullstackgtmSecurity.test.ts`).
|
|
|
72
73
|
|
|
73
74
|
## Releasing (maintainers)
|
|
74
75
|
|
|
75
|
-
The
|
|
76
|
-
|
|
77
|
-
the monorepo:
|
|
76
|
+
The steps are below (deeper rationale lives in `docs/open-core-boundary.md` in
|
|
77
|
+
the development monorepo). From the monorepo:
|
|
78
78
|
|
|
79
79
|
1. Bump `packages/fullstackgtm/package.json` version + add a `CHANGELOG.md`
|
|
80
80
|
entry; merge to `main`.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "fullstackgtm",
|
|
3
|
-
"version": "0.28.
|
|
3
|
+
"version": "0.28.3",
|
|
4
4
|
"description": "Open-source agentic GTM ops framework: canonical GTM data model, pluggable deterministic audits, reviewable dry-run patch plans, approval-gated write-back with conflict detection, and cross-system entity resolution. HubSpot, Salesforce, and Stripe connectors included.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"author": "Full Stack GTM LLC <ryan@fullstackgtm.com> (https://fullstackgtm.com)",
|