Skip to content

Commit

Permalink
Change: Use semver instead of calver for python-gvm releases
Browse files Browse the repository at this point in the history
We decided to use semantic instead if calendar versioning with the next
release. This will allow to declare API compatibility constrains with
every release.
  • Loading branch information
bjoernricks committed Jan 29, 2025
1 parent 22e1951 commit e09c4a7
Show file tree
Hide file tree
Showing 2 changed files with 27 additions and 12 deletions.
12 changes: 0 additions & 12 deletions .github/workflows/release-pontos.yml

This file was deleted.

27 changes: 27 additions & 0 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
name: Release python-gvm

on:
pull_request:
types: [closed]
workflow_dispatch:
inputs:
release-type:
type: choice
description: "Release type. One of patch, minor or major"
options:
- patch
- minor
- major
release-version:
description: "Set an explicit version, that will overwrite release-type. Fails if version is not compliant."
type: string

jobs:
build-and-release:
name: Create a new release
uses: greenbone/workflows/.github/workflows/release-generic.yml@main
with:
versioning-scheme: semver
release-type: ${{ inputs.release-type }}
release-version: ${{ inputs.release-version }}
secrets: inherit

0 comments on commit e09c4a7

Please sign in to comment.