Skip to content

feat: bump spec to v0.1.0-rc.2 (schedule assignment id)#3

Merged
jeroenrinzema merged 1 commit into
mainfrom
feat/schedule-assignment-id
Jun 30, 2026
Merged

feat: bump spec to v0.1.0-rc.2 (schedule assignment id)#3
jeroenrinzema merged 1 commit into
mainfrom
feat/schedule-assignment-id

Conversation

@jeroenrinzema

Copy link
Copy Markdown
Contributor

Tracks platform release v0.1.0-rc.2. The only spec change since rc.1 is the schedule assignment id feature.

What changed

Schedule assignments are now addressable by their own id:

  • Upsert (user.scheduled.post / organization.scheduled.post): set id to update a specific assignment in place, or omit it to create a new one — the same name can now be scheduled multiple times. The id is returned in the response.
  • Delete (user.scheduled.delete / organization.scheduled.delete): set id to remove a single assignment; omit it to delete every assignment by name (unchanged). name is now optional.

How

  • spec/SOURCE.md pinned to v0.1.0-rc.2; spec/client.yaml re-vendored from the release asset (byte-identical to the published spec).
  • Regenerated src/lunogram/gen/models.py (datamodel-code-generator, Python 3.12 — matching CI). The scheduled request models gain an optional id.
  • No facade change: methods already accept a model or dict and _serialize emits id via model_dump(mode="json", exclude_none=True).

make check-drift (regen matches committed) and pytest pass (44 passed, e2e skipped without creds).

Tracks platform release v0.1.0-rc.2. Schedule assignments are now addressable by
their own id: set `id` on an upsert to update a specific assignment in place, or
omit it to create a new one (the same name can be scheduled multiple times). The
returned id can be used to reschedule or delete that instance. Delete now also
accepts an `id` to remove a single assignment instead of all by name.

- spec/SOURCE.md pinned to v0.1.0-rc.2; spec/client.yaml re-vendored
- regenerated src/lunogram/gen/models.py (datamodel-code-generator, py3.12);
  the scheduled request models gain an optional `id` (and delete `name` is now
  optional). The facade passes models/dicts through unchanged.
@jeroenrinzema jeroenrinzema merged commit 1865915 into main Jun 30, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant