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

What should be included in v0.7.2 #373

Closed
Huxpro opened this issue Sep 29, 2020 · 15 comments
Closed

What should be included in v0.7.2 #373

Huxpro opened this issue Sep 29, 2020 · 15 comments
Assignees
Labels

Comments

@Huxpro
Copy link
Contributor

Huxpro commented Sep 29, 2020

This issue is to discuss which fixes should be backported to the next patch release 0.7.2.

EDIT: Since RN 0.64-rc1 has already branched out using 0.7.1, we'll mention this release for RN 0.64 as v0.7.2.

@dulinriley
Copy link
Contributor

dulinriley commented Sep 29, 2020

I'll have a couple of fixes for the memory profiler that are coming soon. I'd like to get as many of these into v0.7.2 as possible so people on RN 0.64 can use the profiler:

  • Fix for multiple native call layers: b7177cb
  • Add script ID to heap timeline output: ea2b5aa
  • More to come later...

@grabbou
Copy link
Contributor

grabbou commented Sep 30, 2020

Just a note that we would prefer the package to be released to CocoaPods repository, just like Flipper is. Is this something you and your team would be able to handle internally? Or do you want me to send a PR to update the CI/release?

@mhorowitz
Copy link
Contributor

mhorowitz commented Oct 1, 2020

Nobody on our team knows anything about how CocoaPods works. According to @alloy, there is no CP repository, it just points to files stored elsewhere. If someone can point to documentation on how this works, it would help a lot. I did some google searching, and did not find any step by step directions. Ideally whatever artifacts are required would be built by CircleCI. If we then need to do some work to publish them to GitHub and update CocoaPods, we can do that, once we learn what to do.

@mhorowitz
Copy link
Contributor

mhorowitz commented Oct 1, 2020

Issue and other crash fixes:
4a0538a
2201966
8cb935c
4108bf9
ba8c4f6
2f07b10
addd6b8
5d08b6e

@alloy
Copy link
Contributor

alloy commented Oct 1, 2020

Nobody on our team knows anything about how CocoaPods works. According to @alloy, there is no CP repository, it just points to files stored elsewhere. If someone can point to documentation on how this works, it would help a lot.

Will respond to this in #368 👍

@dulinriley
Copy link
Contributor

Fix for CVE-2020-1914: b2021df

@Huxpro Huxpro self-assigned this Oct 2, 2020
@Huxpro Huxpro changed the title What should be included in v0.7.2 What should be included in v0.7.3 Nov 9, 2020
@Huxpro Huxpro changed the title What should be included in v0.7.3 What should be included in v0.7.2 (now 0.7.3) Nov 9, 2020
@Huxpro Huxpro changed the title What should be included in v0.7.2 (now 0.7.3) What should be included in v0.7.2 (now v0.7.3) Nov 9, 2020
@janicduplessis
Copy link

Fix optional chaining parsing after a function call b61f164

@Huxpro Huxpro pinned this issue Nov 10, 2020
@Huxpro Huxpro changed the title What should be included in v0.7.2 (now v0.7.3) What should be included in v0.7.2 Dec 8, 2020
@Huxpro
Copy link
Contributor Author

Huxpro commented Dec 8, 2020

Waiting for CI...
OK the CI breaks. Something related to Proxy is not compiled. Marc might forget some intermediate commits here.

@Huxpro
Copy link
Contributor Author

Huxpro commented Dec 8, 2020

Turns out we missed 7d3c17f

@Huxpro
Copy link
Contributor Author

Huxpro commented Dec 9, 2020

The release has been made on the Github release page. I was able to ensure the rn-tester is working perfectly on Android so the npm packages have also been published.

But I hit some issues with pushing to CocoaPod when I was doing:

env hermes-artifact-url='https://github.com/facebook/hermes/releases/download/v0.7.2/hermes-runtime-darwin-v0.7.2.tar.gz' \ 
pod trunk push hermes-engine.podspec

The verbose output is pasted as a gist.

cc-ed @alloy for help.

Work Required

@alloy
Copy link
Contributor

alloy commented Dec 9, 2020

@Huxpro Can you try pod trunk push with the --skip-import-validation flag? Related thread CocoaPods/CocoaPods#10065.

@Huxpro
Copy link
Contributor Author

Huxpro commented Dec 10, 2020

Great! --skip-import-validation did the trick!

Updating spec repo `trunk`
Validating podspec
/Users/jsx/github/hermes/hermes-engine.podspec:8: warning: already initialized constant Pod::HermesHelper::BUILD_TYPE
/Users/jsx/github/hermes/hermes-engine.podspec:8: warning: previous definition of BUILD_TYPE was here
/Users/jsx/github/hermes/hermes-engine.podspec:8: warning: already initialized constant Pod::HermesHelper::BUILD_TYPE
/Users/jsx/github/hermes/hermes-engine.podspec:8: warning: previous definition of BUILD_TYPE was here
 -> hermes-engine (0.7.2)

Updating spec repo `trunk`

--------------------------------------------------------------------------------
 🎉  Congrats

 🚀  hermes-engine (0.7.2) successfully published
 📅  December 9th, 17:28
 🌎  https://cocoapods.org/pods/hermes-engine
 👍  Tell your friends!
--------------------------------------------------------------------------------

[!] Skipping compilation with `xcodebuild` because target contains no sources.

@Huxpro
Copy link
Contributor Author

Huxpro commented Dec 10, 2020

I can verify 0.7.2 is working with USE_HERMES=1 bundle exec pod install --repo-update 🎉

@alloy
Copy link
Contributor

alloy commented Dec 10, 2020

Nice one ✨

@janicduplessis
Copy link

Awesome, I just tested it and I can confirm it fixes the optional chaining issue. I just realized I forgot to remove my script to fix the missing min version key in the framework plist so I haven’t tested that yet.

@Huxpro Huxpro unpinned this issue Dec 15, 2020
@Huxpro Huxpro added the release label Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants