Skip to content

chore: remove v prefix from release tags#99

Merged
marandaneto merged 1 commit into
mainfrom
chore/remove-v-prefix-from-release-tags
Apr 20, 2026
Merged

chore: remove v prefix from release tags#99
marandaneto merged 1 commit into
mainfrom
chore/remove-v-prefix-from-release-tags

Conversation

@marandaneto

Copy link
Copy Markdown
Member

💡 Motivation and Context

This ports the same release-workflow fix from posthog-go to posthog-elixir. The workflow currently creates GitHub releases with a v prefix, but this repo should publish plain semantic version tags/releases like 1.2.3.

💚 How did you test it?

  • ruby -e 'require "yaml"; YAML.load_file(".github/workflows/release.yml"); puts "yaml-ok"'
  • git diff --check

📝 Checklist

  • I reviewed the submitted code.
  • I added tests to verify the changes.
  • I updated the docs if needed.
  • No breaking change or entry added to the changelog.

If releasing new changes

  • Ran sampo add to generate a changeset file
  • Added the release label to the PR

@marandaneto marandaneto requested review from a team and rafaeelaudibert as code owners April 20, 2026 07:14
@marandaneto marandaneto enabled auto-merge (squash) April 20, 2026 07:15
@github-actions

Copy link
Copy Markdown
Contributor

posthog-elixir Compliance Report

Date: 2026-04-20 07:15:15 UTC
Duration: 191ms

⚠️ Some Tests Failed

0/1 tests passed, 1 failed


Feature_Flags Tests

⚠️ 0/1 tests passed, 1 failed

View Details
Test Status Duration
Request Payload.Request With Person Properties Device Id 6ms

Failures

request_payload.request_with_person_properties_device_id

404, message='Not Found', url='http://sdk-adapter:8080/get_feature_flag'

@marandaneto marandaneto merged commit 2beae38 into main Apr 20, 2026
23 checks passed
@marandaneto marandaneto deleted the chore/remove-v-prefix-from-release-tags branch April 20, 2026 08:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants