Skip to content

Upgrade parse from 3.0.0 to 3.1.0 - #7222

Merged
dplewis merged 2 commits into
masterfrom
parse-3.1.0
Feb 24, 2021
Merged

Upgrade parse from 3.0.0 to 3.1.0#7222
dplewis merged 2 commits into
masterfrom
parse-3.1.0

Conversation

@dplewis

@dplewis dplewis commented Feb 24, 2021 •
edited
Loading

Copy link
Copy Markdown
Member

@codecov

codecov Bot commented Feb 24, 2021 •
edited
Loading

Copy link
Copy Markdown

Codecov Report

Merging #7222 (86c9f27) into master (ec8f784) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #7222   +/-   ##
=======================================
  Coverage   94.01%   94.01%           
=======================================
  Files         172      172           
  Lines       12873    12873           
=======================================
  Hits        12103    12103           
  Misses        770      770

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ec8f784...2f78c7d. Read the comment docs.

mtrezza
mtrezza approved these changes Feb 24, 2021
View reviewed changes

@mtrezza mtrezza left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need a changelog entry? Makes me wonder, how do we currently inform about Parse Server <-> Parse JS SDK compatibility?

@dplewis

dplewis commented Feb 24, 2021

Copy link
Copy Markdown
Member Author

We did keep track of the SDK version in the changelog (as well as other deps) a while ago. We removed it in favor of users can check the version through tags.

@mtrezza

mtrezza commented Feb 24, 2021

Copy link
Copy Markdown
Member

Can you explain? - I am thinking of: the docs say for certain features "available from parse server version x.y". But how would a developer know which Parse JS SDK version is required for the feature?

@dplewis

dplewis commented Feb 24, 2021 •
edited
Loading

Copy link
Copy Markdown
Member Author

They should always be using the latest version. The JS SDK doc / guide also has versions per features (May be incomplete). They can also check the JS SDK change logs. git blame is my favorite

@dplewis
dplewis requested a review from davimacedo February 24, 2021 15:53
@mtrezza

mtrezza commented Feb 24, 2021

Copy link
Copy Markdown
Member

Thanks, got it.

@dplewis
dplewis merged commit c4aadc9 into master Feb 24, 2021
@dplewis
dplewis deleted the parse-3.1.0 branch February 24, 2021 16:51
@dplewis dplewis mentioned this pull request Feb 24, 2021
Open
@parseplatformorg

parseplatformorg commented Nov 1, 2021

Copy link
Copy Markdown
Contributor

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

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label Nov 1, 2021
@parseplatformorg

parseplatformorg commented Mar 14, 2022

Copy link
Copy Markdown
Contributor

🎉 This change has been released in version 5.0.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Mar 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mtrezza mtrezza mtrezza approved these changes
@davimacedo davimacedo Awaiting requested review from davimacedo

Assignees

No one assigned

Labels

state:released Released as stable version state:released-beta Released as beta version

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@dplewis @mtrezza @parseplatformorg