Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • GlitchTip Backend GlitchTip Backend
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GlitchTip
  • GlitchTip BackendGlitchTip Backend
  • Issues
  • #145
Closed
Open
Created May 16, 2022 by Ben Stähli@benzkji👁

Version strategy for backend/frontend

When self hosting without docker, I have added the two required repos as git submodules in my "container" git repos. I then wondered what versions work together - hopefully master and master (what I'm using now, but hopefully not in the future ;-), but otherwise, version numbers look different? backend is at 1.9.0, whereas frontend is at 1.12.2 (looking at git tags).

I guess tags got lost on backend? When updating the submodules, it is nice to be able to just pick a tag with the same name, like "v1.12.1", and update both submodules.

Assignee
Assign to
Time tracking