fix: update set config event

[avichalp]

Updates set config events related to recallnet/ipc#522

[sanderpick]

looks good!

@dtbuchholz are we okay to just keep making changes here? i see some tags on this repo... are those used for versioning by the JS repo?

[dtbuchholz]

@sanderpick huh, idk why tags are being added or when that started occurring. afaik, no, those tags arent used anywhere.

the js repo uses this contracts repo as a submodule—no tags used

[sanderpick]

maybe @sam701 or @joewagner added the tags? it would be nice if this repo published an NPM package with JS bindings, similar to what we did in evm-tableland. ie, tag and publish w/ a job: https://github.com/tablelandnetwork/evm-tableland/blob/main/.github/workflows/publish.yml

[dtbuchholz]

this is the js-recall package, for reference—we could definitely migrate it over here: https://github.com/recallnet/js-recall/tree/main/packages/contracts.

[sanderpick]

oh i see. nah i think what you did is good. just so long as there is a way we can continue to push to this repo and not break the JS tooling

[joewagner]

maybe @sam701 or @joewagner added the tags? it would be nice if this repo published an NPM package with JS bindings, similar to what we did in evm-tableland. ie, tag and publish w/ a job: https://github.com/tablelandnetwork/evm-tableland/blob/main/.github/workflows/publish.yml

I didn't add any tags here, but using tags to keep things clear sounds like a reasonable idea. For example, whatever version commit hash is being used in the js-recall submodule would have a tag (in this repo).

[sam701]

@sanderpick yes, I tag all our repos on every subnet reset, as we defined in the subnet reset process in notion.