Skip to content

chore: public-release polish — license, CI, community files, README#1

Merged
owenwahlgren merged 5 commits into
mainfrom
chore/public-release-polish
May 26, 2026
Merged

chore: public-release polish — license, CI, community files, README#1
owenwahlgren merged 5 commits into
mainfrom
chore/public-release-polish

Conversation

@owenwahlgren

Copy link
Copy Markdown
Collaborator

Summary

Gets the repo ready to flip public on github.com/ava-labs/interchain-kit. Three logical changes:

  • Align package.json license fields with the actual LICENSE (BSD-3-Clause). Every package.json previously declared MIT; examples/ had no license field at all.
  • Add .github/ community-health setup: CI workflow (forge test + TS typecheck), CONTRIBUTING.md, SECURITY.md, CODE_OF_CONDUCT.md (Contributor Covenant v2.1), bug-report + feature-request issue templates, PR template.
  • README polish: disambiguate the avalanchego graft/subnet-evm prereq (graft/ lives in the avalanchego checkout, not in this repo), call out the subnet-evm plugin VM ID for users to verify, add a Troubleshooting section, and soften tmpnetjs README's CLI framing (the package isn't on npm — drive it via pnpm run up or the direct bin path).

What changed

  • package.json × 5 → BSD-3-Clause
  • .github/workflows/ci.yml (forge test + typecheck; pins forge-std@v1.9.4, openzeppelin-contracts-upgradeable@v5.0.2, icm-contracts@v1.0.9, recursive submodule init for subnet-evm)
  • CONTRIBUTING.md, SECURITY.md, CODE_OF_CONDUCT.md
  • .github/ISSUE_TEMPLATE/{bug_report,feature_request}.md, .github/PULL_REQUEST_TEMPLATE.md
  • README.md (prereq clarity + Troubleshooting)
  • packages/tmpnetjs/README.md (CLI framing)

How to verify

  • CI run on this PR is green (first run will validate the forge install pins resolve correctly, especially the nested subnet-evm submodule inside lib/icm-contracts)
  • pnpm install --frozen-lockfile clean locally (verified)
  • Confirm security@avalabs.org is the right CoC enforcement contact (currently uses the security inbox — people-ops may prefer a different address)
  • Confirm secondary email in SECURITY.md (icm-contracts/avalanchego only advertise Immunefi)
  • Enable GitHub Discussions on the repo (CONTRIBUTING.md links to it) or remove the link

Not in this PR (manual followups)

  • Logo asset: README.md still points at a github.com/user-attachments/... URL that only resolves for the original uploader. Save the logo locally to docs/logo.png and update line 2 of the README to ./docs/logo.png.

LICENSE is BSD-3-Clause but every package.json declared MIT (and
examples/ had no license field at all). Fix all five to match.
- .github/workflows/ci.yml: forge test + ts typecheck on push/PR
- CONTRIBUTING.md, SECURITY.md, CODE_OF_CONDUCT.md (Contributor Covenant v2.1)
- bug_report / feature_request issue templates + PR template

Standard community-health setup for a public ava-labs repo.
…s CLI framing

- Disambiguate the graft/subnet-evm build step (graft/ lives in the
  avalanchego checkout, not in this repo); call out the subnet-evm
  plugin VM ID so users can verify the plugin landed.
- New Troubleshooting section covering common first-run failures:
  AVALANCHEGO_PATH, missing plugin, stale state, missing forge, ports.
- packages/tmpnetjs/README.md: note the package is not on npm; use
  pnpm scripts or direct bin invocation from the repo, not a global CLI.
`forge install --no-git` strips the .git directory of cloned deps,
which then breaks recursive submodule init inside icm-contracts
(it depends on subnet-evm as a git submodule). Symptom in CI:

  fatal: not a git repository: ../../.git/modules/lib/subnet-evm

Clone the three deps directly with --recurse-submodules instead —
no forge magic, predictable behavior.
Apply canonical forge fmt to bring the tree in line with the
new CI fmt check.
@owenwahlgren owenwahlgren merged commit c787a62 into main May 26, 2026
5 checks passed
@owenwahlgren owenwahlgren deleted the chore/public-release-polish branch May 26, 2026 18:23
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