chore(deps): bump rubykatzen/starcast from 0.2 to 0.7

[dependabot]

Bumps rubykatzen/starcast from 0.2 to 0.7.

Release notes

Sourced from rubykatzen/starcast's releases.

v0.7.0

Changed

• Breaking:proposal-lifecycle-shared.yml is renamed to proposal-shared.yml, matching the <name>-shared.yml pattern used by the other reusable workflows. The workflow's name: and its Telegram-report workflow: value change from "Proposal Lifecycle" to "Proposal", and its concurrency group prefixes shorten from proposal-lifecycle-* to proposal-*.

v0.6.0

Added

• proposal-lifecycle-shared.yml reusable workflow: the contract for the five-job proposal lifecycle (apply, reject, distill, rework, propose) described in #11, with self-gating, an input-invariant check, and per-comment/per-repository concurrency groups. Domain logic for each action is not implemented yet — this release ships the contract and reporting scaffold only.
• actions/telegram-notify composite action: optionally report a job's triggered action and outcome to a Telegram chat (#46). Opt-in per consumer; a missing chat id/bot token is a no-op and a delivery failure never fails the calling job.

v0.5.0

Added

• collect-pull-requests-shared.yml reusable workflow and actions/collect-pull-requests composite action: collect open pull requests, including drafts, from configured organizations/repositories into a GitHub Project V2. Existing active and archived Project items are left untouched, and Status is owned by Project automation.

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue are renamed to collect-issues-shared.yml and actions/collect-issues for consistent naming across issue and pull-request collection.

v0.4.0

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue replace the comma-separated organizations and repos inputs with JSON-array organizations and repositories inputs.

v0.3.1

Removed

... (truncated)

Changelog

Sourced from rubykatzen/starcast's changelog.

Changelog

[Unreleased]

Added

• actions/proposal composite action: a single Homebrew-style CLI (proposal.py <mode> --flag value) covering the whole proposal lifecycle's deterministic surface — dequeue, list-fields, propose, apply, reject — sharing transport, field-discovery, and mutation helpers instead of one script per action.
  • dequeue: consumer-owned capacity_query/queue_query gate and source the next proposal candidate, one per run — see capacity_query/queue_query/review_limit inputs on proposal-shared.yml's propose job. capacity_query must alias exactly one scalar numeric field as capacity, queue_query exactly one array-valued field as queue; both are found by a recursive, type-disambiguated alias search rather than a schema-aware mapping. The dequeued candidate's own id is found the same recursive way, not a flat lookup — needed for queue shapes where id is nested (e.g. a Project-based queue_query typically exposes it as content { ... on Issue { id } }).
  • list-fields: discovers the prefixed proposal Issue Fields available in a repository.
  • propose: creates a proposal issue against a parent — Issue Type, sub-issue relationship, field values, and the control comment. Field values are mocked (a trivial type-appropriate placeholder) rather than agent-decided; real regulation-constrained judgment is tracked in #11.
  • apply/reject: unchanged behavior from the actions they replace (below), now reached via mode: apply/mode: reject.
• proposal-shared.yml's propose job now dequeues a candidate and creates a (mocked) proposal for it, instead of a placeholder notice.
• entity_query, propose_transition_mutation, and apply_transition_mutation inputs on proposal-shared.yml: optionally transition whatever "controlling entity" tracks an issue's state (e.g. a ProjectV2Item) as it moves through the lifecycle — incoming to review on propose, review to done on apply (#69). All three are independently optional consumer-owned GraphQL text; entity_query uses the same alias+type extraction as capacity/queue. A configured transition mutation that fails after a successful create/apply is a hard error, not swallowed.

Changed

• Breaking:actions/apply-proposal and actions/reject-proposal (added in v0.8.0) are removed; their behavior moves to actions/proposal with mode: apply/mode: reject.
• proposal-shared.yml's validate job now also requires capacity_query/queue_query/review_limit on schedule/

... (truncated)

Commits

• 416b3e1 chore: update changelog for v0.7.0 (#52)
• 5739557 Merge pull request #51 from rubykatzen/fix/proposal-rename-breaking-changelog
• d12d606 docs: correct v0.6.0 changelog and bump to v0.7 after rename
• d25f68c Merge pull request #50 from rubykatzen/rename/proposal-shared
• 841d133 rename: proposal-lifecycle-shared.yml to proposal-shared.yml
• ee1498d Merge pull request #49 from rubykatzen/release/v0.6.0
• f84b12b chore: update changelog for v0.6.0
• 6a960ff Merge pull request #48 from rubykatzen/feat/proposal-lifecycle-contract
• b01a32a fix: declare explicit permissions on proposal-lifecycle-shared.yml
• 4702801 Merge remote-tracking branch 'origin/main' into feat/proposal-lifecycle-contract
• Additional commits viewable in compare view

[dependabot]

Superseded by #81.

[dependabot]

Bumps rubykatzen/starcast from 0.2 to 0.7.

Release notes

Sourced from rubykatzen/starcast's releases.

v0.7.0

Changed

• Breaking:proposal-lifecycle-shared.yml is renamed to proposal-shared.yml, matching the <name>-shared.yml pattern used by the other reusable workflows. The workflow's name: and its Telegram-report workflow: value change from "Proposal Lifecycle" to "Proposal", and its concurrency group prefixes shorten from proposal-lifecycle-* to proposal-*.

v0.6.0

Added

• proposal-lifecycle-shared.yml reusable workflow: the contract for the five-job proposal lifecycle (apply, reject, distill, rework, propose) described in #11, with self-gating, an input-invariant check, and per-comment/per-repository concurrency groups. Domain logic for each action is not implemented yet — this release ships the contract and reporting scaffold only.
• actions/telegram-notify composite action: optionally report a job's triggered action and outcome to a Telegram chat (#46). Opt-in per consumer; a missing chat id/bot token is a no-op and a delivery failure never fails the calling job.

v0.5.0

Added

• collect-pull-requests-shared.yml reusable workflow and actions/collect-pull-requests composite action: collect open pull requests, including drafts, from configured organizations/repositories into a GitHub Project V2. Existing active and archived Project items are left untouched, and Status is owned by Project automation.

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue are renamed to collect-issues-shared.yml and actions/collect-issues for consistent naming across issue and pull-request collection.

v0.4.0

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue replace the comma-separated organizations and repos inputs with JSON-array organizations and repositories inputs.

v0.3.1

Removed

... (truncated)

Changelog

Sourced from rubykatzen/starcast's changelog.

Changelog

[Unreleased]

Added

• actions/proposal composite action: a single Homebrew-style CLI (proposal.py <mode> --flag value) covering the whole proposal lifecycle's deterministic surface — dequeue, list-fields, propose, apply, reject — sharing transport, field-discovery, and mutation helpers instead of one script per action.
  • dequeue: consumer-owned capacity_query/queue_query gate and source the next proposal candidate, one per run — see capacity_query/queue_query/review_limit inputs on proposal-shared.yml's propose job. capacity_query must alias exactly one scalar numeric field as capacity, queue_query exactly one array-valued field as queue; both are found by a recursive, type-disambiguated alias search rather than a schema-aware mapping. The dequeued candidate's own id is found the same recursive way, not a flat lookup — needed for queue shapes where id is nested (e.g. a Project-based queue_query typically exposes it as content { ... on Issue { id } }).
  • list-fields: discovers the prefixed proposal Issue Fields available in a repository.
  • propose: creates a proposal issue against a parent — Issue Type, sub-issue relationship, field values, and the control comment. Field values are mocked (a trivial type-appropriate placeholder) rather than agent-decided; real regulation-constrained judgment is tracked in #11.
  • apply/reject: unchanged behavior from the actions they replace (below), now reached via mode: apply/mode: reject.
• proposal-shared.yml's propose job now dequeues a candidate and creates a (mocked) proposal for it, instead of a placeholder notice.
• entity_query, propose_transition_mutation, and apply_transition_mutation inputs on proposal-shared.yml: optionally transition whatever "controlling entity" tracks an issue's state (e.g. a ProjectV2Item) as it moves through the lifecycle — incoming to review on propose, review to done on apply (#69). All three are independently optional consumer-owned GraphQL text; entity_query uses the same alias+type extraction as capacity/queue. A configured transition mutation that fails after a successful create/apply is a hard error, not swallowed.

Changed

• Breaking:actions/apply-proposal and actions/reject-proposal (added in v0.8.0) are removed; their behavior moves to actions/proposal with mode: apply/mode: reject.
• proposal-shared.yml's validate job now also requires capacity_query/queue_query/review_limit on schedule/

... (truncated)

Commits

• 416b3e1 chore: update changelog for v0.7.0 (#52)
• 5739557 Merge pull request #51 from rubykatzen/fix/proposal-rename-breaking-changelog
• d12d606 docs: correct v0.6.0 changelog and bump to v0.7 after rename
• d25f68c Merge pull request #50 from rubykatzen/rename/proposal-shared
• 841d133 rename: proposal-lifecycle-shared.yml to proposal-shared.yml
• ee1498d Merge pull request #49 from rubykatzen/release/v0.6.0
• f84b12b chore: update changelog for v0.6.0
• 6a960ff Merge pull request #48 from rubykatzen/feat/proposal-lifecycle-contract
• b01a32a fix: declare explicit permissions on proposal-lifecycle-shared.yml
• 4702801 Merge remote-tracking branch 'origin/main' into feat/proposal-lifecycle-contract
• Additional commits viewable in compare view

[dependabot]

Superseded by #81.

[dependabot]

Bumps rubykatzen/starcast from 0.2 to 0.7.

Release notes

Sourced from rubykatzen/starcast's releases.

v0.7.0

Changed

• Breaking:proposal-lifecycle-shared.yml is renamed to proposal-shared.yml, matching the <name>-shared.yml pattern used by the other reusable workflows. The workflow's name: and its Telegram-report workflow: value change from "Proposal Lifecycle" to "Proposal", and its concurrency group prefixes shorten from proposal-lifecycle-* to proposal-*.

v0.6.0

Added

• proposal-lifecycle-shared.yml reusable workflow: the contract for the five-job proposal lifecycle (apply, reject, distill, rework, propose) described in #11, with self-gating, an input-invariant check, and per-comment/per-repository concurrency groups. Domain logic for each action is not implemented yet — this release ships the contract and reporting scaffold only.
• actions/telegram-notify composite action: optionally report a job's triggered action and outcome to a Telegram chat (#46). Opt-in per consumer; a missing chat id/bot token is a no-op and a delivery failure never fails the calling job.

v0.5.0

Added

• collect-pull-requests-shared.yml reusable workflow and actions/collect-pull-requests composite action: collect open pull requests, including drafts, from configured organizations/repositories into a GitHub Project V2. Existing active and archived Project items are left untouched, and Status is owned by Project automation.

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue are renamed to collect-issues-shared.yml and actions/collect-issues for consistent naming across issue and pull-request collection.

v0.4.0

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue replace the comma-separated organizations and repos inputs with JSON-array organizations and repositories inputs.

v0.3.1

Removed

... (truncated)

Changelog

Sourced from rubykatzen/starcast's changelog.

Changelog

[Unreleased]

Added

• actions/proposal composite action: a single Homebrew-style CLI (proposal.py <mode> --flag value) covering the whole proposal lifecycle's deterministic surface — dequeue, list-fields, propose, apply, reject — sharing transport, field-discovery, and mutation helpers instead of one script per action.
  • dequeue: consumer-owned capacity_query/queue_query gate and source the next proposal candidate, one per run — see capacity_query/queue_query/review_limit inputs on proposal-shared.yml's propose job. capacity_query must alias exactly one scalar numeric field as capacity, queue_query exactly one array-valued field as queue; both are found by a recursive, type-disambiguated alias search rather than a schema-aware mapping. The dequeued candidate's own id is found the same recursive way, not a flat lookup — needed for queue shapes where id is nested (e.g. a Project-based queue_query typically exposes it as content { ... on Issue { id } }).
  • list-fields: discovers the prefixed proposal Issue Fields available in a repository.
  • propose: creates a proposal issue against a parent — Issue Type, sub-issue relationship, field values, and the control comment. Field values are mocked (a trivial type-appropriate placeholder) rather than agent-decided; real regulation-constrained judgment is tracked in #11.
  • apply/reject: unchanged behavior from the actions they replace (below), now reached via mode: apply/mode: reject.
• proposal-shared.yml's propose job now dequeues a candidate and creates a (mocked) proposal for it, instead of a placeholder notice.
• entity_query, propose_transition_mutation, and apply_transition_mutation inputs on proposal-shared.yml: optionally transition whatever "controlling entity" tracks an issue's state (e.g. a ProjectV2Item) as it moves through the lifecycle — incoming to review on propose, review to done on apply (#69). All three are independently optional consumer-owned GraphQL text; entity_query uses the same alias+type extraction as capacity/queue. A configured transition mutation that fails after a successful create/apply is a hard error, not swallowed.

Changed

• Breaking:actions/apply-proposal and actions/reject-proposal (added in v0.8.0) are removed; their behavior moves to actions/proposal with mode: apply/mode: reject.
• proposal-shared.yml's validate job now also requires capacity_query/queue_query/review_limit on schedule/

... (truncated)

Commits

• 416b3e1 chore: update changelog for v0.7.0 (#52)
• 5739557 Merge pull request #51 from rubykatzen/fix/proposal-rename-breaking-changelog
• d12d606 docs: correct v0.6.0 changelog and bump to v0.7 after rename
• d25f68c Merge pull request #50 from rubykatzen/rename/proposal-shared
• 841d133 rename: proposal-lifecycle-shared.yml to proposal-shared.yml
• ee1498d Merge pull request #49 from rubykatzen/release/v0.6.0
• f84b12b chore: update changelog for v0.6.0
• 6a960ff Merge pull request #48 from rubykatzen/feat/proposal-lifecycle-contract
• b01a32a fix: declare explicit permissions on proposal-lifecycle-shared.yml
• 4702801 Merge remote-tracking branch 'origin/main' into feat/proposal-lifecycle-contract
• Additional commits viewable in compare view

[dependabot]

Superseded by #81.

[dependabot]

Bumps rubykatzen/starcast from 0.2 to 0.7.

Release notes

Sourced from rubykatzen/starcast's releases.

v0.7.0

Changed

• Breaking:proposal-lifecycle-shared.yml is renamed to proposal-shared.yml, matching the <name>-shared.yml pattern used by the other reusable workflows. The workflow's name: and its Telegram-report workflow: value change from "Proposal Lifecycle" to "Proposal", and its concurrency group prefixes shorten from proposal-lifecycle-* to proposal-*.

v0.6.0

Added

• proposal-lifecycle-shared.yml reusable workflow: the contract for the five-job proposal lifecycle (apply, reject, distill, rework, propose) described in #11, with self-gating, an input-invariant check, and per-comment/per-repository concurrency groups. Domain logic for each action is not implemented yet — this release ships the contract and reporting scaffold only.
• actions/telegram-notify composite action: optionally report a job's triggered action and outcome to a Telegram chat (#46). Opt-in per consumer; a missing chat id/bot token is a no-op and a delivery failure never fails the calling job.

v0.5.0

Added

• collect-pull-requests-shared.yml reusable workflow and actions/collect-pull-requests composite action: collect open pull requests, including drafts, from configured organizations/repositories into a GitHub Project V2. Existing active and archived Project items are left untouched, and Status is owned by Project automation.

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue are renamed to collect-issues-shared.yml and actions/collect-issues for consistent naming across issue and pull-request collection.

v0.4.0

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue replace the comma-separated organizations and repos inputs with JSON-array organizations and repositories inputs.

v0.3.1

Removed

... (truncated)

Changelog

Sourced from rubykatzen/starcast's changelog.

Changelog

[Unreleased]

Added

• actions/proposal composite action: a single Homebrew-style CLI (proposal.py <mode> --flag value) covering the whole proposal lifecycle's deterministic surface — dequeue, list-fields, propose, apply, reject — sharing transport, field-discovery, and mutation helpers instead of one script per action.
  • dequeue: consumer-owned capacity_query/queue_query gate and source the next proposal candidate, one per run — see capacity_query/queue_query/review_limit inputs on proposal-shared.yml's propose job. capacity_query must alias exactly one scalar numeric field as capacity, queue_query exactly one array-valued field as queue; both are found by a recursive, type-disambiguated alias search rather than a schema-aware mapping. The dequeued candidate's own id is found the same recursive way, not a flat lookup — needed for queue shapes where id is nested (e.g. a Project-based queue_query typically exposes it as content { ... on Issue { id } }).
  • list-fields: discovers the prefixed proposal Issue Fields available in a repository.
  • propose: creates a proposal issue against a parent — Issue Type, sub-issue relationship, field values, and the control comment. Field values are mocked (a trivial type-appropriate placeholder) rather than agent-decided; real regulation-constrained judgment is tracked in #11.
  • apply/reject: unchanged behavior from the actions they replace (below), now reached via mode: apply/mode: reject.
• proposal-shared.yml's propose job now dequeues a candidate and creates a (mocked) proposal for it, instead of a placeholder notice.
• entity_query, propose_transition_mutation, and apply_transition_mutation inputs on proposal-shared.yml: optionally transition whatever "controlling entity" tracks an issue's state (e.g. a ProjectV2Item) as it moves through the lifecycle — incoming to review on propose, review to done on apply (#69). All three are independently optional consumer-owned GraphQL text; entity_query uses the same alias+type extraction as capacity/queue. A configured transition mutation that fails after a successful create/apply is a hard error, not swallowed.

Changed

• Breaking:actions/apply-proposal and actions/reject-proposal (added in v0.8.0) are removed; their behavior moves to actions/proposal with mode: apply/mode: reject.
• proposal-shared.yml's validate job now also requires capacity_query/queue_query/review_limit on schedule/

... (truncated)

Commits

• 416b3e1 chore: update changelog for v0.7.0 (#52)
• 5739557 Merge pull request #51 from rubykatzen/fix/proposal-rename-breaking-changelog
• d12d606 docs: correct v0.6.0 changelog and bump to v0.7 after rename
• d25f68c Merge pull request #50 from rubykatzen/rename/proposal-shared
• 841d133 rename: proposal-lifecycle-shared.yml to proposal-shared.yml
• ee1498d Merge pull request #49 from rubykatzen/release/v0.6.0
• f84b12b chore: update changelog for v0.6.0
• 6a960ff Merge pull request #48 from rubykatzen/feat/proposal-lifecycle-contract
• b01a32a fix: declare explicit permissions on proposal-lifecycle-shared.yml
• 4702801 Merge remote-tracking branch 'origin/main' into feat/proposal-lifecycle-contract
• Additional commits viewable in compare view

[dependabot]

Superseded by #81.

[dependabot]

Bumps rubykatzen/starcast from 0.2 to 0.7.

Release notes

Sourced from rubykatzen/starcast's releases.

v0.7.0

Changed

• Breaking:proposal-lifecycle-shared.yml is renamed to proposal-shared.yml, matching the <name>-shared.yml pattern used by the other reusable workflows. The workflow's name: and its Telegram-report workflow: value change from "Proposal Lifecycle" to "Proposal", and its concurrency group prefixes shorten from proposal-lifecycle-* to proposal-*.

v0.6.0

Added

• proposal-lifecycle-shared.yml reusable workflow: the contract for the five-job proposal lifecycle (apply, reject, distill, rework, propose) described in #11, with self-gating, an input-invariant check, and per-comment/per-repository concurrency groups. Domain logic for each action is not implemented yet — this release ships the contract and reporting scaffold only.
• actions/telegram-notify composite action: optionally report a job's triggered action and outcome to a Telegram chat (#46). Opt-in per consumer; a missing chat id/bot token is a no-op and a delivery failure never fails the calling job.

v0.5.0

Added

• collect-pull-requests-shared.yml reusable workflow and actions/collect-pull-requests composite action: collect open pull requests, including drafts, from configured organizations/repositories into a GitHub Project V2. Existing active and archived Project items are left untouched, and Status is owned by Project automation.

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue are renamed to collect-issues-shared.yml and actions/collect-issues for consistent naming across issue and pull-request collection.

v0.4.0

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue replace the comma-separated organizations and repos inputs with JSON-array organizations and repositories inputs.

v0.3.1

Removed

... (truncated)

Changelog

Sourced from rubykatzen/starcast's changelog.

Changelog

[Unreleased]

Added

• actions/proposal composite action: a single Homebrew-style CLI (proposal.py <mode> --flag value) covering the whole proposal lifecycle's deterministic surface — dequeue, list-fields, propose, apply, reject — sharing transport, field-discovery, and mutation helpers instead of one script per action.
  • dequeue: consumer-owned capacity_query/queue_query gate and source the next proposal candidate, one per run — see capacity_query/queue_query/review_limit inputs on proposal-shared.yml's propose job. capacity_query must alias exactly one scalar numeric field as capacity, queue_query exactly one array-valued field as queue; both are found by a recursive, type-disambiguated alias search rather than a schema-aware mapping. The dequeued candidate's own id is found the same recursive way, not a flat lookup — needed for queue shapes where id is nested (e.g. a Project-based queue_query typically exposes it as content { ... on Issue { id } }).
  • list-fields: discovers the prefixed proposal Issue Fields available in a repository.
  • propose: creates a proposal issue against a parent — Issue Type, sub-issue relationship, field values, and the control comment. Field values are mocked (a trivial type-appropriate placeholder) rather than agent-decided; real regulation-constrained judgment is tracked in #11.
  • apply/reject: unchanged behavior from the actions they replace (below), now reached via mode: apply/mode: reject.
• proposal-shared.yml's propose job now dequeues a candidate and creates a (mocked) proposal for it, instead of a placeholder notice.
• entity_query, propose_transition_mutation, and apply_transition_mutation inputs on proposal-shared.yml: optionally transition whatever "controlling entity" tracks an issue's state (e.g. a ProjectV2Item) as it moves through the lifecycle — incoming to review on propose, review to done on apply (#69). All three are independently optional consumer-owned GraphQL text; entity_query uses the same alias+type extraction as capacity/queue. A configured transition mutation that fails after a successful create/apply is a hard error, not swallowed.

Changed

• Breaking:actions/apply-proposal and actions/reject-proposal (added in v0.8.0) are removed; their behavior moves to actions/proposal with mode: apply/mode: reject.
• proposal-shared.yml's validate job now also requires capacity_query/queue_query/review_limit on schedule/

... (truncated)

Commits

• 416b3e1 chore: update changelog for v0.7.0 (#52)
• 5739557 Merge pull request #51 from rubykatzen/fix/proposal-rename-breaking-changelog
• d12d606 docs: correct v0.6.0 changelog and bump to v0.7 after rename
• d25f68c Merge pull request #50 from rubykatzen/rename/proposal-shared
• 841d133 rename: proposal-lifecycle-shared.yml to proposal-shared.yml
• ee1498d Merge pull request #49 from rubykatzen/release/v0.6.0
• f84b12b chore: update changelog for v0.6.0
• 6a960ff Merge pull request #48 from rubykatzen/feat/proposal-lifecycle-contract
• b01a32a fix: declare explicit permissions on proposal-lifecycle-shared.yml
• 4702801 Merge remote-tracking branch 'origin/main' into feat/proposal-lifecycle-contract
• Additional commits viewable in compare view

[dependabot]

Superseded by #81.

[dependabot]

Bumps rubykatzen/starcast from 0.2 to 0.7.

Release notes

Sourced from rubykatzen/starcast's releases.

v0.7.0

Changed

• Breaking:proposal-lifecycle-shared.yml is renamed to proposal-shared.yml, matching the <name>-shared.yml pattern used by the other reusable workflows. The workflow's name: and its Telegram-report workflow: value change from "Proposal Lifecycle" to "Proposal", and its concurrency group prefixes shorten from proposal-lifecycle-* to proposal-*.

v0.6.0

Added

• proposal-lifecycle-shared.yml reusable workflow: the contract for the five-job proposal lifecycle (apply, reject, distill, rework, propose) described in #11, with self-gating, an input-invariant check, and per-comment/per-repository concurrency groups. Domain logic for each action is not implemented yet — this release ships the contract and reporting scaffold only.
• actions/telegram-notify composite action: optionally report a job's triggered action and outcome to a Telegram chat (#46). Opt-in per consumer; a missing chat id/bot token is a no-op and a delivery failure never fails the calling job.

v0.5.0

Added

• collect-pull-requests-shared.yml reusable workflow and actions/collect-pull-requests composite action: collect open pull requests, including drafts, from configured organizations/repositories into a GitHub Project V2. Existing active and archived Project items are left untouched, and Status is owned by Project automation.

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue are renamed to collect-issues-shared.yml and actions/collect-issues for consistent naming across issue and pull-request collection.

v0.4.0

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue replace the comma-separated organizations and repos inputs with JSON-array organizations and repositories inputs.

v0.3.1

Removed

... (truncated)

Changelog

Sourced from rubykatzen/starcast's changelog.

Changelog

[Unreleased]

Added

• actions/proposal composite action: a single Homebrew-style CLI (proposal.py <mode> --flag value) covering the whole proposal lifecycle's deterministic surface — dequeue, list-fields, propose, apply, reject — sharing transport, field-discovery, and mutation helpers instead of one script per action.
  • dequeue: consumer-owned capacity_query/queue_query gate and source the next proposal candidate, one per run — see capacity_query/queue_query/review_limit inputs on proposal-shared.yml's propose job. capacity_query must alias exactly one scalar numeric field as capacity, queue_query exactly one array-valued field as queue; both are found by a recursive, type-disambiguated alias search rather than a schema-aware mapping. The dequeued candidate's own id is found the same recursive way, not a flat lookup — needed for queue shapes where id is nested (e.g. a Project-based queue_query typically exposes it as content { ... on Issue { id } }).
  • list-fields: discovers the prefixed proposal Issue Fields available in a repository.
  • propose: creates a proposal issue against a parent — Issue Type, sub-issue relationship, field values, and the control comment. Field values are mocked (a trivial type-appropriate placeholder) rather than agent-decided; real regulation-constrained judgment is tracked in #11.
  • apply/reject: unchanged behavior from the actions they replace (below), now reached via mode: apply/mode: reject.
• proposal-shared.yml's propose job now dequeues a candidate and creates a (mocked) proposal for it, instead of a placeholder notice.
• entity_query, propose_transition_mutation, and apply_transition_mutation inputs on proposal-shared.yml: optionally transition whatever "controlling entity" tracks an issue's state (e.g. a ProjectV2Item) as it moves through the lifecycle — incoming to review on propose, review to done on apply (#69). All three are independently optional consumer-owned GraphQL text; entity_query uses the same alias+type extraction as capacity/queue. A configured transition mutation that fails after a successful create/apply is a hard error, not swallowed.

Changed

• Breaking:actions/apply-proposal and actions/reject-proposal (added in v0.8.0) are removed; their behavior moves to actions/proposal with mode: apply/mode: reject.
• proposal-shared.yml's validate job now also requires capacity_query/queue_query/review_limit on schedule/

... (truncated)

Commits

• 416b3e1 chore: update changelog for v0.7.0 (#52)
• 5739557 Merge pull request #51 from rubykatzen/fix/proposal-rename-breaking-changelog
• d12d606 docs: correct v0.6.0 changelog and bump to v0.7 after rename
• d25f68c Merge pull request #50 from rubykatzen/rename/proposal-shared
• 841d133 rename: proposal-lifecycle-shared.yml to proposal-shared.yml
• ee1498d Merge pull request #49 from rubykatzen/release/v0.6.0
• f84b12b chore: update changelog for v0.6.0
• 6a960ff Merge pull request #48 from rubykatzen/feat/proposal-lifecycle-contract
• b01a32a fix: declare explicit permissions on proposal-lifecycle-shared.yml
• 4702801 Merge remote-tracking branch 'origin/main' into feat/proposal-lifecycle-contract
• Additional commits viewable in compare view

[dependabot]

Superseded by #81.

[dependabot]

Bumps rubykatzen/starcast from 0.2 to 0.7.

Release notes

Sourced from rubykatzen/starcast's releases.

v0.7.0

Changed

• Breaking:proposal-lifecycle-shared.yml is renamed to proposal-shared.yml, matching the <name>-shared.yml pattern used by the other reusable workflows. The workflow's name: and its Telegram-report workflow: value change from "Proposal Lifecycle" to "Proposal", and its concurrency group prefixes shorten from proposal-lifecycle-* to proposal-*.

v0.6.0

Added

• proposal-lifecycle-shared.yml reusable workflow: the contract for the five-job proposal lifecycle (apply, reject, distill, rework, propose) described in #11, with self-gating, an input-invariant check, and per-comment/per-repository concurrency groups. Domain logic for each action is not implemented yet — this release ships the contract and reporting scaffold only.
• actions/telegram-notify composite action: optionally report a job's triggered action and outcome to a Telegram chat (#46). Opt-in per consumer; a missing chat id/bot token is a no-op and a delivery failure never fails the calling job.

v0.5.0

Added

• collect-pull-requests-shared.yml reusable workflow and actions/collect-pull-requests composite action: collect open pull requests, including drafts, from configured organizations/repositories into a GitHub Project V2. Existing active and archived Project items are left untouched, and Status is owned by Project automation.

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue are renamed to collect-issues-shared.yml and actions/collect-issues for consistent naming across issue and pull-request collection.

v0.4.0

Changed

• Breaking:pull-issue-shared.yml and actions/pull-issue replace the comma-separated organizations and repos inputs with JSON-array organizations and repositories inputs.

v0.3.1

Removed

... (truncated)

Changelog

Sourced from rubykatzen/starcast's changelog.

Changelog

[Unreleased]

Added

• actions/proposal composite action: a single Homebrew-style CLI (proposal.py <mode> --flag value) covering the whole proposal lifecycle's deterministic surface — dequeue, list-fields, propose, apply, reject — sharing transport, field-discovery, and mutation helpers instead of one script per action.
  • dequeue: consumer-owned capacity_query/queue_query gate and source the next proposal candidate, one per run — see capacity_query/queue_query/review_limit inputs on proposal-shared.yml's propose job. capacity_query must alias exactly one scalar numeric field as capacity, queue_query exactly one array-valued field as queue; both are found by a recursive, type-disambiguated alias search rather than a schema-aware mapping. The dequeued candidate's own id is found the same recursive way, not a flat lookup — needed for queue shapes where id is nested (e.g. a Project-based queue_query typically exposes it as content { ... on Issue { id } }).
  • list-fields: discovers the prefixed proposal Issue Fields available in a repository.
  • propose: creates a proposal issue against a parent — Issue Type, sub-issue relationship, field values, and the control comment. Field values are mocked (a trivial type-appropriate placeholder) rather than agent-decided; real regulation-constrained judgment is tracked in #11.
  • apply/reject: unchanged behavior from the actions they replace (below), now reached via mode: apply/mode: reject.
• proposal-shared.yml's propose job now dequeues a candidate and creates a (mocked) proposal for it, instead of a placeholder notice.
• entity_query, propose_transition_mutation, and apply_transition_mutation inputs on proposal-shared.yml: optionally transition whatever "controlling entity" tracks an issue's state (e.g. a ProjectV2Item) as it moves through the lifecycle — incoming to review on propose, review to done on apply (#69). All three are independently optional consumer-owned GraphQL text; entity_query uses the same alias+type extraction as capacity/queue. A configured transition mutation that fails after a successful create/apply is a hard error, not swallowed.

Changed

• Breaking:actions/apply-proposal and actions/reject-proposal (added in v0.8.0) are removed; their behavior moves to actions/proposal with mode: apply/mode: reject.
• proposal-shared.yml's validate job now also requires capacity_query/queue_query/review_limit on schedule/

... (truncated)

Commits

• 416b3e1 chore: update changelog for v0.7.0 (#52)
• 5739557 Merge pull request #51 from rubykatzen/fix/proposal-rename-breaking-changelog
• d12d606 docs: correct v0.6.0 changelog and bump to v0.7 after rename
• d25f68c Merge pull request #50 from rubykatzen/rename/proposal-shared
• 841d133 rename: proposal-lifecycle-shared.yml to proposal-shared.yml
• ee1498d Merge pull request #49 from rubykatzen/release/v0.6.0
• f84b12b chore: update changelog for v0.6.0
• 6a960ff Merge pull request #48 from rubykatzen/feat/proposal-lifecycle-contract
• b01a32a fix: declare explicit permissions on proposal-lifecycle-shared.yml
• 4702801 Merge remote-tracking branch 'origin/main' into feat/proposal-lifecycle-contract
• Additional commits viewable in compare view

[dependabot]

Superseded by #81.