Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Switch to semantic versioning (semver) compatible versioning pattern #52

Closed
atc0005 opened this issue Mar 5, 2023 · 0 comments · Fixed by #65
Closed

Switch to semantic versioning (semver) compatible versioning pattern #52

atc0005 opened this issue Mar 5, 2023 · 0 comments · Fixed by #65
Assignees
@atc0005
Labels
builds config dependencies enhancement New feature or request
Milestone
v0.2.0

Comments

@atc0005
Copy link
Owner

atc0005 commented Mar 5, 2023

Overview

Update generated assets to use a semver compatible pattern for::

  • filenames (where applicable)
  • embedded version metadata

References
@atc0005 atc0005 added enhancement New feature or request builds config labels Mar 5, 2023
@atc0005 atc0005 added this to the Next minor release milestone Mar 5, 2023
@atc0005 atc0005 self-assigned this Mar 5, 2023
atc0005 added a commit that referenced this issue Mar 7, 2023
@atc0005
Refactor project build process
61590ca 
- Switch to semantic versioning (semver) compatible versioning pattern
  - filenames (where applicable)
  - embedded version metadata
- Generate RPM/DEB packages using nFPM
  - "stable" release packages
  - "dev" release packages
    - provides binaries with `_dev` suffix in order to more easily
      test the impact of new releases
- Add version metadata to Windows executables
  - Use `github.com/tc-hib/go-winres` and `winres.json` file to apply
    version details to Windows executables provided by this project
    - NOTE: This is future planning; this project does not currently
      provide Windows binaries (this support is not present yet)
  - update `.gitignore` to exclude Windows syso files
    - these files are produced when running go generate as part of the
      build process and should not be retained in version control
- Makefile: Compress binaries and use fixed filenames
- Makefile: Refresh recipes to add "standard" set, new package-related
  options
- Build dev/stable releases using go-ci Docker image
- Add Dockerfile to provide "builder" image for Makefile-driven
  release builds
- Update Dependabot configuration to add update monitoring for
  `go-ci-oldstable-build` image
- Add Docker-based build recipes to Makefile
  - `docker-release-build`
  - `docker-dev-build`
  - `docker-packages`
- Update README
  - note decompression step needed after downloading individual
    binaries or building via some Makefile recipes
  - note DEB and RPM packages as alternatives to downloading
    individual binaries

refs GH-52
refs GH-53
refs GH-54
refs GH-55
refs GH-56
refs GH-57
@atc0005 atc0005 mentioned this issue Mar 7, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@atc0005 atc0005

Labels
builds config dependencies enhancement New feature or request
Projects
None yet
Milestone
v0.2.0
Development

Successfully merging a pull request may close this issue.

Refactor project build process atc0005/check-process
1 participant
@atc0005