Add `rc` channel for betas and release candidates

conda-forge / spyder-feedstock

A conda-smithy repository for spyder.

BSD 3-Clause "New" or "Revised" License

1 stars 17 forks source link

Add `rc` channel for betas and release candidates #189

Closed ccordoba12 closed 2 weeks ago

ccordoba12 commented 1 month ago

Checklist

[x] 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)
[x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

We need this to publish release candidates before new stable releases, or betas and rc's of minor/major ones.

ccordoba12 commented 1 month ago

@conda-forge-admin, please rerender

github-actions[bot] commented 1 month ago

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

I Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory.

github-actions[bot] commented 1 month ago

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.

ccordoba12 commented 1 month ago

@conda-forge-admin, please rerender

mrclary commented 1 month ago

@ccordoba12, is there a reason why spyder_dev channel cannot be used for release candidates?

ccordoba12 commented 3 weeks ago

@ccordoba12, is there a reason why spyder_dev channel cannot be used for release candidates?

According to the Conda-forge docs, we should use a spyder_rc channel for betas and rc's.

Do you think that would cause issues to the way we build our installers?

mrclary commented 3 weeks ago

@ccordoba12, is there a reason why spyder_dev channel cannot be used for release candidates?

According to the Conda-forge docs, we should use a spyder_rc channel for betas and rc's.

Do you think that would cause issues to the way we build our installers?

That should not cause any issues, I'll just have to update the channels in our build scripts and workflows. Currently they are looking at conda-forge/label/spyder_dev. I'll just have to update those to conda-forge/label/spyder_rc.

ccordoba12 commented 2 weeks ago

Ok, no worries. I'll do that in a PR that I'm preparing to update our release instructions.