Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove RERUN_IS_PUBLISHING and bump to 0.10.0 #17

Merged
merged 7 commits into from
Oct 30, 2023

Conversation

jleibs
Copy link
Contributor

@jleibs jleibs commented Oct 26, 2023

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.

Combined with the changes from:

This fixes:

RERUN_IS_PUBLISHING is used for the crate publishing and Rerun now handles this properly by checking for the CONDA_BUILD environment variable.

Note: this fix won't actually work until we release rerun-0.10 with the fix from rerun-io/rerun#4015

@jleibs jleibs requested a review from ruben-arts as a code owner October 26, 2023 00:18
@conda-forge-webservices
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 (recipe) and found it was in an excellent condition.

@ruben-arts
Copy link
Contributor

I guess this requires the merge of the PR mentioned in the description right? You can also test it locally to change the source in the meta.yaml to a local version and run the build_locally.py

teh-cmc pushed a commit to rerun-io/rerun that referenced this pull request Oct 26, 2023
…ilt artifacts (#4015)

Resolves:
 - #3908

The main issue is that the conda environment dind't realize it was
building a released version.

The conda build environment is special. The feedstock recipe downloads
the source from the published artifact, so many of our checks related to
things like branch-name aren't correct. Otherwise it's very close to the
CI build environment.

This detects the environment and attempts to do more reasonable things
where relevant.

### Testing
- I created a temporary branch in the rerun feedstock repository
pointing to the source
`https://github.com/rerun-io/rerun/archive/refs/heads/jleibs/conda_examples.zip`
- I built using `python build-locally.py
linux_64_python3.10.____cpython`
- I ran the `rerun` version from the channel with `RUST_LOG=debug`
- Confirmed correct attempted download location based on version:
- `Downloading .rrd file from
"https://demo.rerun.io/version/0.10.0-alpha.7+dev/examples/plots/data.rrd"…`

Related, I also need to remove RERUN_IS_PUBLISHING from the conda
recipe. See:
 - conda-forge/rerun-sdk-feedstock#17
@jleibs jleibs changed the title Remove RERUN_IS_PUBLISHING Remove RERUN_IS_PUBLISHING and bump to 0.10.0 Oct 30, 2023
@jleibs jleibs merged commit 83497ac into conda-forge:main Oct 30, 2023
17 checks passed
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