Skip to content

build: Release beta #1658

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

Merged
merged 46 commits into from
Jan 23, 2023
Merged

build: Release beta #1658

merged 46 commits into from
Jan 23, 2023

Conversation

mtrezza
Copy link
Member

@mtrezza mtrezza commented Jan 20, 2023

No description provided.

dblythy and others added 30 commits November 6, 2022 16:30
BREAKING CHANGE: This release removes support for Node versions <14
# [4.0.0-alpha.1](parse-community/Parse-SDK-JS@3.5.1-alpha.2...4.0.0-alpha.1) (2022-11-10)

### Bug Fixes

* Remove support for Node <14 ([parse-community#1603](parse-community#1603)) ([bc04b4b](parse-community@bc04b4b))

### BREAKING CHANGES

* This release removes support for Node versions <14 ([bc04b4b](bc04b4b))
…error in Cloud Code Triggers `beforeConnect` or `beforeSubscribe` (parse-community#1490)

BREAKING CHANGE: Calling `Parse.Query.subscribe()` will now return a rejected promise if an error is thrown in Cloud Code Triggers `beforeConnect` or `beforeSubscribe`; in previous releases a resolved promise was returned, even if subscribing failed and it was necessary to create an `error.on` listener to handle these errors (parse-community#1490)
# [4.0.0-alpha.2](parse-community/Parse-SDK-JS@4.0.0-alpha.1...4.0.0-alpha.2) (2022-11-15)

### Bug Fixes

* `Parse.Query.subscribe()` does not return a rejected promise on error in Cloud Code Triggers `beforeConnect` or `beforeSubscribe` ([parse-community#1490](parse-community#1490)) ([96d7174](parse-community@96d7174))

### BREAKING CHANGES

* Calling `Parse.Query.subscribe()` will now return a rejected promise if an error is thrown in Cloud Code Triggers `beforeConnect` or `beforeSubscribe`; in previous releases a resolved promise was returned, even if subscribing failed and it was necessary to create an `error.on` listener to handle these errors (parse-community#1490) ([96d7174](96d7174))
# [4.0.0-alpha.3](parse-community/Parse-SDK-JS@4.0.0-alpha.2...4.0.0-alpha.3) (2022-11-18)

### Performance Improvements

* Avoid CORS preflight request by removing upload listener when not used ([parse-community#1610](parse-community#1610)) ([6125419](parse-community@6125419))
@parse-github-assistant
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title build: release beta build: Release beta Jan 20, 2023
@parse-github-assistant
Copy link

Thanks for opening this pull request!

  • ❌ Please edit your post and use the provided template when creating a new pull request. This helps everyone to understand your post better and asks for essential information to quicker review the pull request.

@codecov
Copy link

codecov bot commented Jan 20, 2023

Codecov Report

Base: 99.93% // Head: 99.89% // Decreases project coverage by -0.04% ⚠️

Coverage data is based on head (5b31b9f) compared to base (f32b3b1).
Patch coverage: 90.47% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             beta    #1658      +/-   ##
==========================================
- Coverage   99.93%   99.89%   -0.04%     
==========================================
  Files          61       61              
  Lines        5966     5973       +7     
  Branches     1366     1367       +1     
==========================================
+ Hits         5962     5967       +5     
- Misses          4        6       +2     
Impacted Files Coverage Δ
src/LiveQueryClient.js 98.99% <81.81%> (-1.01%) ⬇️
src/ParseQuery.js 100.00% <100.00%> (ø)
src/RESTController.js 100.00% <100.00%> (ø)
src/StorageController.react-native.js 100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@mtrezza
Copy link
Member Author

mtrezza commented Jan 20, 2023

@dblythy did we forget anything here in the node 16 CI? the node 16 tests are consistently failing with connection errors. could you take a look?

@dblythy
Copy link
Member

dblythy commented Jan 21, 2023

I will investigate

@mtrezza
Copy link
Member Author

mtrezza commented Jan 21, 2023

Interestingly, the Node 16 tests for the latest commit on the alpha branch seemed to pass except for one flaky test. So it's strange this is failing in this PR where the only difference is commit 5b31b9f. It may be something that occurs due to the merge.

@mtrezza mtrezza mentioned this pull request Jan 22, 2023
@mtrezza mtrezza merged commit 4e94c2d into parse-community:beta Jan 23, 2023
@mtrezza
Copy link
Member Author

mtrezza commented Jan 23, 2023

Ran the Node 16 tests again and they passed except for 1 flaky test. There may be some other issue with the CI. Going ahead and merging.

@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.0.0-beta.1

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label Jan 23, 2023
@mtrezza mtrezza deleted the release-beta branch January 23, 2023 19:15
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.0.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Jan 23, 2023
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.0.0-alpha.6

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Jan 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released Released as stable version state:released-alpha Released as alpha version state:released-beta Released as beta version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants