Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A arch-boxes
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch Linux
  • arch-boxes
  • Issues
  • #101

Closed
Open
Created May 05, 2020 by Sven-Hendrik Haase@svenstaroContributor

[Question] What's the relationship between a "Release" on GitHub and a "Version" on Vagrant Cloud?

Created by: PaulWalkerUK

On Github, when I look at the releases for this project, I see the last couple were 1.4.0 on 3 Jan and 1.5.0 on 4 Mar.

When I look on Vagrant Cloud, I see versions v2020.05.05, v2020.05.02, v2020.04.02, etc, all with no description, but varying sizes, so it appears that they are different, but no clue about what's changed.

What is the relationship between creating a release on Github and making a new version available on Vagrant Cloud?

Is there anyway of knowing what exactly what Github version a particular Vagrant release was built from?

Edited Sep 26, 2020 by Sven-Hendrik Haase
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking