Skip to content

Commit a126d1a

Browse files
committed
v0.35.0-beta
1 parent dbc1377 commit a126d1a

File tree

3 files changed

+5
-9
lines changed

3 files changed

+5
-9
lines changed

README.md

+2-6
Original file line numberDiff line numberDiff line change
@@ -14,14 +14,10 @@ should be reverted to not use the dev-master branch.
1414
*Some packages, like HydeFront may not need to have their tags synced. Thinking it is mainly for
1515
hyde/hyde and hyde/framework as they are tightly coupled.
1616

17-
Update: (my notes)
18-
Okay here is where I am at. At this point I don't want to spend a ton of time crafting intricate CI workflows when I don't yet know if the whole monorepo thing is gonna pan out. So my idea is as follows, I'll try using this repo as the source of truth, but as I want the packages to have a git history that makes sense, I will primarly make the "real" commits within them. This version control in this repo will then more function to track and sync states. But actual releases might be handled in the subpackages as I'm not sure how easily I can sync tags and create releases (without adding a ton of complexity at least). However this causes me to still need to make commits in both the subrepositor and main one which is not ideal. I would want to create the commits in the monorepo and then have all those propagated without generic messages like "monorepo commit". This could be remedied by using pull requests to perform merges, and listing all the commits in containing changes for the subrepo. (this worked nice `git log --since="5 days ago" -- .\packages\framework\ > log`, see https://github.com/hydephp/framework/pull/534)
19-
20-
Update 2: Okay so how it works now, changes pushed to master will be propagated to readonly branche mirrors, with the commit messages. I can then manually create pull requests in the actual package repositories. The latter part of which I can automate.
21-
2217
## Warning
2318

24-
This monorepo project is **highly experimental** and **unstable**!
19+
This monorepo project is **highly experimental** and **unstable**!
20+
Changes pushed to the actual package repositories are only made when stable.
2521

2622
## Projects in this monorepo
2723

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
@@ -8,7 +8,7 @@
88
"dependencies": {},
99
"name": "hyde",
1010
"description": "Elegant and Powerful Static App Builder",
11-
"version": "0.34.0",
11+
"version": "0.35.0",
1212
"main": "hyde",
1313
"directories": {
1414
"test": "tests"

0 commit comments

Comments
 (0)