Skip to content

Versioning of zlinter #20

@KurtWagner

Description

@KurtWagner

How this is versioned will eventually need some thought. For now it's simply split between two branches

  1. master for zig master (currently 0.15-dev)
  2. 0.14.x for zig 0.14 latest (currently 0.14.1)

with zlinter remaining at 0.0.1 in its build.zig.zon between changes being submitted (regardless of whether there are breaking changes). Development simply occurs branched from one of these and commits are cherrypicked across as changes aim to be zig version agnostic.

A downside to this is there is no linter specific version metadata attached to the version so you may get an updated version between calling zig fetch without what changed being super obvious


Some open questions:

  1. Version in GitHub with releases, tags or branches?
  2. Should the version in Github differ from zig build zon? (e.g., zon could be base 0.1.2 and GitHub could be a build number or timestamp or commit)

Metadata

Metadata

Assignees

No one assigned

    Labels

    designSomething needing thoughtopen to discussionOpen to thoughts and opinions

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions