Skip to content

docs: no CHANGELOG.md despite an explicit CONTRACT_VERSION constant #309

Closed

Description

@Austinaminu2

Problem

No `CHANGELOG.md` exists despite the contract defining an explicit `CONTRACT_VERSION` constant (`contracts/streaming/src/lib.rs:55`) and a `migrate()` function implying the contract has already gone through version transitions.

Location

repo root (missing file), `contracts/streaming/src/lib.rs:55`

Impact

There's no way for users or integrators to see what changed between contract or app releases, despite the codebase clearly being versioned internally.

Suggested fix

Add a `CHANGELOG.md` following a standard format (e.g. Keep a Changelog), and start documenting entries going forward, backfilling major past changes if feasible from git history.

Activity

  1. sagesan2580 commented on Jul 23, 2026

    @sagesan2580

    @sagesan2580 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

    Hi maintainer, can I pick up this issue?

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @sagesan2580 to this issue.

  2. SYMBAxx commented on Jul 23, 2026

    @SYMBAxx
    Contributor

    @SYMBAxx has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

    can i please take this on

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @SYMBAxx to this issue.

  3. drips-wave commented on Jul 23, 2026

    @drips-wave

    Congratulations, @SYMBAxx! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

    🧑‍💻 @SYMBAxx: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  4. added a commit that references this issue on Jul 23, 2026
    f886672
  5. grantfox-oss commented on Jul 24, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

    @SYMBAxx's PR #318 was approved and merged by @Austinaminu2.

    🏆 @SYMBAxx: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (557 total points). Track your full progress on GrantFox.

    👏 Great work, @SYMBAxx! Keep contributing to FlowwStar.

  6. drips-wave commented on Jul 24, 2026

    @drips-wave

    This issue has been completed by @SYMBAxx as part of the Stellar Wave Program's 7th Wave 🥳

    😎 @SYMBAxx: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentation

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions