Skip to content

release: cut v0.70.0 - #11

Merged
trendvidia merged 1 commit into
mainfrom
release/v0.70.0
May 8, 2026
Merged

release: cut v0.70.0#11
trendvidia merged 1 commit into
mainfrom
release/v0.70.0

Conversation

@trendvidia

@trendvidia trendvidia commented May 8, 2026

Copy link
Copy Markdown
Owner

Summary

  • Promote [Unreleased] entries in CHANGELOG.md to [0.70.0] – 2026-05-06.
  • Sets up the spec repo to receive its first git tag, matching the v0.70.x baseline shipping across the 9 sibling ports.

Follow-up (after merge)

  • Tag v0.70.0 at the merge commit.
  • Cut a GitHub release referencing the spec, governance constitution, IETF draft, adversarial corpus, hardening contract, and cross-port harness.

Note for reviewer

Commit needs to be signed — please amend with your GPG key before merging (or merge via squash to re-author from the web UI), since main requires signed commits.

Test plan

  • CI green (CodeQL Go + Java/Kotlin + tests).
  • CHANGELOG renders the new section under the [Unreleased] heading.

@trendvidia
release: cut v0.70.0
1579f5c 
Promote [Unreleased] entries to [0.70.0] – 2026-05-06 in advance of
tagging v0.70.0 on this repo. Matches the v0.70.x baseline already
shipping across the 9 sibling ports.
@trendvidia
trendvidia merged commit 59b6ad7 into main May 8, 2026
4 checks passed
@trendvidia
trendvidia deleted the release/v0.70.0 branch May 8, 2026 08:05
@trendvidia trendvidia mentioned this pull request May 12, 2026
Merged
4 tasks
@trendvidia trendvidia mentioned this pull request Jul 16, 2026
Merged
trendvidia added a commit that referenced this pull request Jul 16, 2026
@trendvidia
spec: pin project-level engine-config format (RFC-001 §9.4) (#95)
401d907 
Resolves spec issue #11 (GH #60).

- proto/schema/config/v1/config.proto: EngineConfig message. Config is
  a textproto file (protowire.config.textproto at project root), not a
  schema-less .proto carrying file options — keeps the no-JSON/YAML
  principle without burning carrier extension numbers or leaking build
  config into FileDescriptorSet artifacts.
- Discovery: upward walk, nearest config wins, no merging (go.mod model).
- Precedence: per-setting CLI flags > --config > PROTOWIRE_CONFIG (file
  pointer only) > discovered file > defaults (cel, lenient, collect-all).
  Unknown engine names are startup errors, never fallbacks.
- default_mode reuses protowire.schema.v1.ExecutionMode from report.proto;
  field 6 earmarked for the #62 recursion-depth knob.
- New RFC-001 §9.4; §13 row 2 resolved; CHANGELOG updated.
- testdata/schema-extensions/08_engine_config.textproto: golden config,
  verified with stock protoc (parse + --encode/--decode round-trip).
@trendvidia trendvidia mentioned this pull request Jul 16, 2026
Merged
trendvidia added a commit that referenced this pull request Jul 16, 2026
@trendvidia
docs: record S1 resolutions (#11–#16) in RFC-001-issues.md
a092a20 
Ticks the six open-question boxes and adds a resolution record to each
section — GH #60–#65, PR train #94–#99 — with pointers to the follow-up
trackers (protocompile#67/#68, GH #102/#103) and the fixtures 07–11.
trendvidia added a commit that referenced this pull request Jul 16, 2026
@trendvidia
spec: pin project-level engine-config format (RFC-001 §9.4) (#105)
6a92b7a 
Resolves spec issue #11 (GH #60).

- proto/schema/config/v1/config.proto: EngineConfig message. Config is
  a textproto file (protowire.config.textproto at project root), not a
  schema-less .proto carrying file options — keeps the no-JSON/YAML
  principle without burning carrier extension numbers or leaking build
  config into FileDescriptorSet artifacts.
- Discovery: upward walk, nearest config wins, no merging (go.mod model).
- Precedence: per-setting CLI flags > --config > PROTOWIRE_CONFIG (file
  pointer only) > discovered file > defaults (cel, lenient, collect-all).
  Unknown engine names are startup errors, never fallbacks.
- default_mode reuses protowire.schema.v1.ExecutionMode from report.proto;
  field 6 earmarked for the #62 recursion-depth knob.
- New RFC-001 §9.4; §13 row 2 resolved; CHANGELOG updated.
- testdata/schema-extensions/08_engine_config.textproto: golden config,
  verified with stock protoc (parse + --encode/--decode round-trip).
trendvidia added a commit that referenced this pull request Jul 16, 2026
@trendvidia
docs: record S1 resolutions (#11–#16) in RFC-001-issues.md
b770291 
Ticks the six open-question boxes and adds a resolution record to each
section — GH #60–#65, PR train #94–#99 — with pointers to the follow-up
trackers (protocompile#67/#68, GH #102/#103) and the fixtures 07–11.
trendvidia added a commit that referenced this pull request Jul 16, 2026
@trendvidia
docs: record S1 resolutions (#11–#16) in RFC-001-issues.md
886eeff 
Ticks the six open-question boxes and adds a resolution record to each
section — GH #60–#65, PR train #94–#99 — with pointers to the follow-up
trackers (protocompile#67/#68, GH #102/#103) and the fixtures 07–11.
trendvidia added a commit that referenced this pull request Jul 16, 2026
@trendvidia
docs: record S1 resolutions (#11–#16) in RFC-001-issues.md
4f27a19 
Ticks the six open-question boxes and adds a resolution record to each
section — GH #60–#65, PR train #94–#99 — with pointers to the follow-up
trackers (protocompile#67/#68, GH #102/#103) and the fixtures 07–11.
trendvidia added a commit that referenced this pull request Jul 16, 2026
@trendvidia
docs: record S1 resolutions (#11–#16) in RFC-001-issues.md
874945a 
Ticks the six open-question boxes and adds a resolution record to each
section — GH #60–#65, PR train #94–#99 — with pointers to the follow-up
trackers (protocompile#67/#68, GH #102/#103) and the fixtures 07–11.
trendvidia added a commit that referenced this pull request Jul 16, 2026
@trendvidia
docs: record S1 resolutions (#11–#16) in RFC-001-issues.md (#104)
eedb373 
* spec: finalize Literal carrier shape (RFC-001 §8.1)

Resolves spec issue #15 (GH #64). In-place revision of the unreleased
carrier — the deliberate pre-freeze window for wire-shape changes.

- EnumLiteral {enum_type, value_name, number}: enum references lower
  RESOLVED; consumers never re-resolve bare names against a pool
  (replaces string enum_name).
- ListLiteral becomes repeated LiteralValue: elements are values, not
  arguments — no names, no expressions representable; homogeneous kind
  required (same enum_type for enum elements); nesting legal.
- Message literals stay google.protobuf.Any, with the explicit-typing
  rule pinned: type from the param declaration or an explicit use-site
  type name, never inferred from value shape; source spelling deferred
  to the IETF draft (#3).
- RFC-001 §8.1 excerpt + lowering rules prose; §13 row 6 resolved;
  CHANGELOG notes the protocompile descriptor.pb.go re-vendor follow-up.
- Fixtures: 10_literal_args.proto (schema-text: enum ref + list on
  any-typed params) and 11_literal_carrier_golden.textproto (lowered
  AnnotationList, all three kinds, protoc encode/decode-verified).

* docs: record S1 resolutions (#11–#16) in RFC-001-issues.md

Ticks the six open-question boxes and adds a resolution record to each
section — GH #60–#65, PR train #94–#99 — with pointers to the follow-up
trackers (protocompile#67/#68, GH #102/#103) and the fixtures 07–11.
trendvidia added a commit that referenced this pull request Jul 16, 2026
@trendvidia
spec: ratify RFC-001 (issue #56) (#113)
bdb1cb7 
* spec: ratify RFC-001 (issue #56)

Status Draft → Ratified (2026-07-16). §13 rows 13/14 now cite their
tracking issues (GH #111, #112) — with those filed, every open
question is either resolved in the RFC (S1: #11–#16; S2: #15
source grammar, #21 sensitivity, #35 path scheme; S3: #22
engine-expression scope, #23 no dual-emission) or tracked as a
separate issue (GH #59, #66–#69, #103, #111, #112). All v1.2 surface
is strictly additive; no locked decision blocks an existing port's
roadmap (per-port adoption is M9+, gated on the conformance corpus).

* docs: record #2 ratification (GH #56, PR #113)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@trendvidia