lint: add new lint rule to enforce version is pinned in `package.name` (if `package.version` specified)

Open
#215 0 comments 0 reactions 2 assignees View on GitHub

@developer-guy is already working on this.

Since May 16, 2023.

Assessment

This issue has not been assessed yet.

Description

enhancement needs-triage

Description

Imagine we want to build the following package:

package:
  name: foo
  version: 1.2.3

We should not allow this since there could be already package named foo that use the latest. Instead it'd be nice to pass if -major.minor is set as suffix.

Valid:

package:
  name: foo-1
  version: 1.2.3

package:
  name: foo-1.2
  version: 1.2.3

package:
  name: foo-1.2.3
  version: 1.2.3

Not valid: (Version mismatch)

package:
  name: foo-2.1
  version: 1.2.3
Dominant language
Go
Stars
73
Forks
86
Avg merge
7d 7h
Merged PRs (30d)
15

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wolfi-dev/wolfictl

All issues in wolfi-dev/wolfictl

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.