Skip to content

Conversation

@tdejager
Copy link
Contributor

@tdejager tdejager commented Nov 6, 2025

Checklist

  • Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
  • License file is packaged (see here for an example).
  • Source is from official source.
  • Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
  • Build number is 0.
  • A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).

This adds the jpm package manager for the janet language, which is also on conda-forge. The recipe contains a number of tests to test that the package manager works as expected.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 6, 2025

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

@conda-forge-admin
Copy link
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 (recipes/jpm/recipe.yaml) and found it was in an excellent condition.

@tdejager tdejager changed the title Add jpm 1.1.0 Add janet package manager (jpm) 1.1.0 Nov 6, 2025
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