Skip to content

Commit dee9680

Browse files
committedJun 5, 2023
chore(release): 1.2.0 [skip ci]
# [1.2.0](1.1.0...1.2.0) (2023-06-05) ### Bug Fixes * **cloud:** just return a string ([#363](#363)) ([4fa5a88](4fa5a88)) ### Features * Update to Parse Server 6 syntax ([#427](#427)) ([36ff42b](36ff42b)) * upgrade to Parse Server 5.2.1 and other dependency upgrades ([#418](#418)) ([96b104f](96b104f))
1 parent c5d170a commit dee9680

File tree

3 files changed

+14
-3
lines changed

3 files changed

+14
-3
lines changed
 

‎CHANGELOG.md

+11
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# [1.2.0](https://github.com/ParsePlatform/parse-server-example/compare/1.1.0...1.2.0) (2023-06-05)
2+
3+
4+
### Bug Fixes
5+
6+
* **cloud:** just return a string ([#363](https://github.com/ParsePlatform/parse-server-example/issues/363)) ([4fa5a88](https://github.com/ParsePlatform/parse-server-example/commit/4fa5a88c8deada01b5326d02bbe2b8c94f4445b2))
7+
8+
### Features
9+
10+
* Update to Parse Server 6 syntax ([#427](https://github.com/ParsePlatform/parse-server-example/issues/427)) ([36ff42b](https://github.com/ParsePlatform/parse-server-example/commit/36ff42b41c1298c36de5cfba89172345eba42894))
11+
* upgrade to Parse Server 5.2.1 and other dependency upgrades ([#418](https://github.com/ParsePlatform/parse-server-example/issues/418)) ([96b104f](https://github.com/ParsePlatform/parse-server-example/commit/96b104f8ca21ea7b091924965cb7269622c4ad4f))

‎package-lock.json

+2-2
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎package.json

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "parse-server-example",
3-
"version": "1.4.0",
3+
"version": "1.2.0",
44
"description": "An example Parse API server using the parse-server module",
55
"repository": {
66
"type": "git",

0 commit comments

Comments
 (0)
Please sign in to comment.