You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way I understand the Conda feedstock workflow, this should be done by first updating our fork of that repo https://github.com/PostHog/posthog-feedstock, making the changes there, then making a PR from our fork to upstream, and merging that. But maybe just a commit should be enough? @posthog-bot is listed as a maintainer of the @conda-forge repo after all.
The text was updated successfully, but these errors were encountered:
We now have a Conda package too (set up by contributor @mands), defined at https://github.com/conda-forge/posthog-feedstock. But https://github.com/PostHog/posthog-python/blob/master/.github/workflows/release.yaml doesn't take it into account, which will cause the package to not be updated for Conda.
Updating the package for Conda would be just editing https://github.com/conda-forge/posthog-feedstock/blob/master/recipe/meta.yaml:
{% set version = "1.4.2" %}
requirements:
The way I understand the Conda feedstock workflow, this should be done by first updating our fork of that repo https://github.com/PostHog/posthog-feedstock, making the changes there, then making a PR from our fork to upstream, and merging that. But maybe just a commit should be enough? @posthog-bot is listed as a maintainer of the @conda-forge repo after all.
The text was updated successfully, but these errors were encountered: