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

Dependencies and releases are not fully checked #48221

Closed
evan1715 opened this issue Dec 11, 2024 · 5 comments
Closed

Dependencies and releases are not fully checked #48221

evan1715 opened this issue Dec 11, 2024 · 5 comments
Labels
Needs: Author Feedback Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. Needs: Version Info Resolution: Answered When the issue is resolved with a simple answer

Comments

@evan1715
Copy link

evan1715 commented Dec 11, 2024

Description

RN 0.76.4 was released previously on Github, but not on NPM a week or so ago. Now fixed, but says 0.76.4 and 0.76.5 were released "2 days ago" on the same date.

RN 0.76.5 does not include package match semver for @react-native/babel-preset, @rreact-native/metro-config, etc for 0.76.5 inside the Upgrade Helper. Leads to confusion as do I match the versioning or do I not.
seen here: https://react-native-community.github.io/upgrade-helper/?from=0.76.4&to=0.76.5

On the same link, there's a non-existent binary on Upgrade Helper.

Hermes dSYMS URLs are not found: https://github.com/facebook/react-native/releases/tag/v0.76.5

Steps to reproduce

N/A

React Native Version

0.76.5

Affected Platforms

Other (please specify)

Output of npx react-native info

N/A

Stacktrace or Logs

N/A

Reproducer

N/A

Screenshots and Videos

N/A

@react-native-bot react-native-bot added Needs: Author Feedback Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. Needs: Version Info labels Dec 11, 2024
@react-native-bot
Copy link
Collaborator

Warning

Could not parse version: We could not find or parse the version number of React Native in your issue report. Please use the template, and report your version including major, minor, and patch numbers - e.g. 0.76.2.

@react-native-bot
Copy link
Collaborator

Warning

Missing reproducer: We could not detect a reproducible example in your issue report. Please provide either:

@react-native-bot
Copy link
Collaborator

Warning

Could not parse version: We could not find or parse the version number of React Native in your issue report. Please use the template, and report your version including major, minor, and patch numbers - e.g. 0.76.2.

@coder-xiaomo
Copy link

same here, upgrate from 0.76.3 to 0.76.5 the upgrade-helper shows the wrong version

https://react-native-community.github.io/upgrade-helper/?from=0.76.3&to=0.76.5

image

@cortinico
Copy link
Contributor

RN 0.76.4 was released previously on Github, but not on NPM a week or so ago. Now fixed, but says 0.76.4 and 0.76.5 were released "2 days ago" on the same date.

Releasing a React Native version is quite of a long progress. I see both 0.76.4 and 0.76.5 are on NPM/GitHub. Please allow some time from when the release ends up on all the various repositories for it to be fully usable.

RN 0.76.5 does not include package match semver for @react-native/babel-preset, @rreact-native/metro-config, etc for 0.76.5 inside the Upgrade Helper. Leads to confusion as do I match the versioning or do I not. seen here: react-native-community.github.io/upgrade-helper?from=0.76.4&to=0.76.5
On the same link, there's a non-existent binary on Upgrade Helper.

That's a bug on the upgrade helper.
See here:

Hermes dSYMS URLs are not found: v0.76.5 (release)

Fixed. There was a type on the URL

@cortinico cortinico added the Resolution: Answered When the issue is resolved with a simple answer label Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Author Feedback Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. Needs: Version Info Resolution: Answered When the issue is resolved with a simple answer
Projects
None yet
Development

No branches or pull requests

4 participants