-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
spidermonkey 115.4.0esr #11
base: main
Are you sure you want to change the base?
Conversation
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 ( |
@conda-forge-admin please rerender |
…nda-forge-pinning 2023.08.24.11.35.19
That's quite cool!
One concern I have is that couchdb is very picky about spidermonkey
versions it supports. I haven't looked into this but it could be tricky to
do updates. But since spidermonkey is the hard part of building couchdb,
having more consumers of spidermonkey seems like a plus.
…On Thu, 24 Aug 2023, 15:19 Nicholas Bollweg ***@***.***> wrote:
Checklist
- Used a personal fork of the feedstock to propose changes
<https://conda-forge.org/docs/maintainer/updating_pkgs.html#forking-and-pull-requests>
- Bumped the build number (if the version is unchanged)
- Reset the build number to 0 (if the version changed)
- Re-rendered
<https://conda-forge.org/docs/maintainer/updating_pkgs.html#rerendering-feedstocks>
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.
Notes:
- blocked by conda-forge/icu-feedstock#41
<conda-forge/icu-feedstock#41>
Motivation:
- conda-forge/staged-recipes#23783
<conda-forge/staged-recipes#23783>
------------------------------
You can view, comment on, or merge this pull request online at:
#11
Commit Summary
- 59e39e4
<59e39e4>
spidermonkey 115.0.3
File Changes
(1 file
<https://github.com/conda-forge/spidermonkey-feedstock/pull/11/files>)
- *M* recipe/meta.yaml
<https://github.com/conda-forge/spidermonkey-feedstock/pull/11/files#diff-f3725a55bf339595bf865fec73bda8ac99f283b0810c205442021f29c06eea9a>
(22)
Patch Links:
- https://github.com/conda-forge/spidermonkey-feedstock/pull/11.patch
- https://github.com/conda-forge/spidermonkey-feedstock/pull/11.diff
—
Reply to this email directly, view it on GitHub
<#11>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABJFIP27MK2YGHYJXW252DXW5IFBANCNFSM6AAAAAA35ASS2Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Yeah, seems like intentional pins would do the job for |
osx needs some updates (will wait and see how linux does):
|
…nda-forge-pinning 2023.08.24.19.16.55
…nda-forge-pinning 2023.08.24.19.16.55
@conda-forge-admin please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub actions workflow run https://github.com/conda-forge/spidermonkey-feedstock/actions/runs/5969728657. |
…nda-forge-pinning 2023.08.24.19.16.55
oof, i didn't realize how fragile the OSX SDK supply chain was: |
Will have another look if we get conda-forge/conda-forge-ci-setup-feedstock#281 in. |
…nda-forge-pinning 2023.09.25.12.55.07
Good to try the latest ESR, but still haven't finished the upstream plumbing... |
@conda-forge-admin please restart ci |
Bah
|
|
…nda-forge-pinning 2023.10.30.10.19.43
…nda-forge-pinning 2023.10.30.10.19.43
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)Notes:
Motivation: