Skip to content

Enable Campaign Mgm Support - #130

Merged
vicentebolea merged 2 commits into
conda-forge:mainfrom
ax3l:fix-build-campaign
Jun 1, 2026
Merged

Enable Campaign Mgm Support#130
vicentebolea merged 2 commits into
conda-forge:mainfrom
ax3l:fix-build-campaign

Conversation

@ax3l

@ax3l ax3l commented Jan 12, 2026

Copy link
Copy Markdown
Member

In its initial release, campaign mgmt created a dot directory alongside our regular outputs, which was very verbose #94. This has since been fixed, and we need campaign mgmt now in new projects.

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

@conda-forge-admin

Copy link
Copy Markdown
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/20932499668. Examine the logs at this URL for more detail.

In its initial release, campaign mgmt created a dot directory
alongside our regular outputs, which was very verbose. This has
since been fixed, and we need campaign mgmt now in new projects.
@conda-forge-admin

Copy link
Copy Markdown
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

@vicentebolea vicentebolea added the automerge Merge the PR when CI passes label Jun 1, 2026
@conda-forge-admin

Copy link
Copy Markdown
Contributor

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

  • linter: passed
  • azure: failed
  • github-actions: failed

Thus the PR was not passing and not merged.

…2026.06.01.13.14.52

Other tools:
- conda-build 26.5.0
- rattler-build 0.65.0
- rattler-build-conda-compat 1.4.14
@conda-forge-curator conda-forge-curator Bot removed the automerge Merge the PR when CI passes label Jun 1, 2026
@conda-forge-admin

Copy link
Copy Markdown
Contributor

Hi! This is the friendly conda-forge automerge bot!

Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

@vicentebolea
vicentebolea merged commit 13f38f7 into conda-forge:main Jun 1, 2026
252 of 253 checks passed
@ax3l
ax3l deleted the fix-build-campaign branch June 1, 2026 22:38
@ax3l ax3l added the enhancement New feature or request label Jun 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants