Skip to content

Conversation

@yhabib
Copy link
Contributor

@yhabib yhabib commented Jul 8, 2025

Motivation

Like in #7079, this PR updates proposals based on the main branch and not a release

Changes

  • Instead of checking for the latest releases, the update-aggregator CI job now checks for any new IC commits.

Tests

  • Tested in

Todos

  • Accessibility (a11y) – any impact?
  • Changelog – is it needed?

@yhabib yhabib changed the title proposals to latest chore: Update Proposals types for potentially any IC commit Jul 8, 2025
@yhabib yhabib force-pushed the yhabib/proposals/latest branch from 09eab73 to 5b6bd84 Compare July 8, 2025 21:43
@yhabib yhabib marked this pull request as ready for review July 8, 2025 21:55
@yhabib yhabib requested a review from a team as a code owner July 8, 2025 21:55
@yhabib yhabib force-pushed the yhabib/proposals/latest branch from 5b6bd84 to 9acb1cf Compare August 14, 2025 08:02
@yhabib yhabib force-pushed the yhabib/proposals/latest branch from 9acb1cf to 0a94acd Compare January 6, 2026 13:04
# Motivation
We would like to render all the latest proposal types.
Even with no changes, just updating the reference is good practice.

# Changes
* Update the version of `IC_COMMIT_FOR_PROPOSALS` specified in
`config.json`.
* Updated the `proposals` candid files to the versions in that commit.
* Updated the Rust code derived from `.did` files in the proposals
payload rendering crate.

# Tests
- [ ] Please check the API updates for any breaking changes that affect
our code.
  - [ ] Please check for new proposal types and add tests for them.

Breaking changes are:
  * New mandatory fields
    * Removing mandatory fields
    * Renaming fields
    * Changing the type of a field
    * Adding new variants

Co-authored-by: gix-bot <[email protected]>
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