Skip to content

Conversation

@mtrezza
Copy link
Member

@mtrezza mtrezza commented Oct 10, 2021

Important

Do not merge this before making sure the branches and version tags are properly prepared. Merge this after release 2.0.0 and before any other PR is merged.

TODO:

  • Remove changelog enforcer from CI

@codecov
Copy link

codecov bot commented Oct 10, 2021

Codecov Report

Merging #1114 (55206cb) into master (d2d3926) will not change coverage.
The diff coverage is n/a.

❗ Current head 55206cb differs from pull request most recent head 8d6151d. Consider uploading reports for the commit 8d6151d to get more accurate results
Impacted file tree graph

@@            Coverage Diff            @@
##             master    #1114   +/-   ##
=========================================
  Coverage     65.06%   65.06%           
  Complexity     2208     2208           
=========================================
  Files           122      122           
  Lines          9463     9463           
  Branches       1317     1317           
=========================================
  Hits           6157     6157           
  Misses         2799     2799           
  Partials        507      507           

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 d2d3926...8d6151d. Read the comment docs.

@mtrezza
Copy link
Member Author

mtrezza commented Oct 10, 2021

@L3K0V do we have any other breaking change to merge before making the 2.0.0 release? So we don't have to release a 3.0 directly after 2.0.

@azlekov
Copy link
Contributor

azlekov commented Oct 10, 2021

I think we are okay for now, no huge changes planned maybe just bug fixes and improvements. I'm considering splitting the modernisation into a little bit more granular steps.

@mtrezza
Copy link
Member Author

mtrezza commented Oct 10, 2021

I'm considering splitting the modernisation into a little bit more granular steps.

That's a good idea, if we can publish these steps, we can open issues for each of them and also assign bounties.

@mtrezza mtrezza merged commit f5009be into parse-community:master Oct 10, 2021
@mtrezza mtrezza deleted the enable-release-automation branch October 10, 2021 19:25
@mtrezza
Copy link
Member Author

mtrezza commented Oct 10, 2021

closing #1116

@mtrezza mtrezza linked an issue Oct 10, 2021 that may be closed by this pull request
@parseplatformorg
Copy link

🎉 This pull request has been released in version 2.0.1

@parseplatformorg parseplatformorg added the state:released Released as stable version label Oct 14, 2021
@parseplatformorg
Copy link

🎉 This pull request has been released in version 2.0.1

1 similar comment
@parseplatformorg
Copy link

🎉 This pull request has been released in version 2.0.1

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

♻️ Release Automation

3 participants