This repository was archived by the owner on Feb 15, 2024. It is now read-only.
build: release beta #18
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## [4.1.3-alpha.1](parse-community/parse-dashboard@4.1.2...4.1.3-alpha.1) (2022-06-18) ### Bug Fixes * security upgrade semver-regex from 3.1.3 to 3.1.4 ([parse-community#2154](parse-community#2154)) ([4f9090a](parse-community@4f9090a))
# [4.2.0-alpha.1](parse-community/parse-dashboard@4.1.3-alpha.1...4.2.0-alpha.1) (2022-07-04) ### Bug Fixes * login fails with error `req.session.regenerate is not a function` ([parse-community#2195](parse-community#2195)) [skip release] ([31a2b78](parse-community@31a2b78)) ### Features * remove support and documentation links ([parse-community#2203](parse-community#2203)) ([35e4476](parse-community@35e4476))
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release beta
This pull request was created because a new release is due according to the release cycle of this repository.
Just resolve any conflicts and it's good to merge. Any version increment will be done by release automation.
Merge committo merge this pull request. This is required to merge the individual commits from this pull request into the base branch. Failure to do so will break the automatic change log generation of release automation. Do not use "Squash and merge"!