Skip to content

chore: bump all#219

Open
SilasPeters wants to merge 1 commit intodevelopmentfrom
chore/bump-all
Open

chore: bump all#219
SilasPeters wants to merge 1 commit intodevelopmentfrom
chore/bump-all

Conversation

@SilasPeters
Copy link
Copy Markdown
Member

Worked on my machine devcontainer

@SilasPeters
Copy link
Copy Markdown
Member Author

Please test if it works on your machine as well. Are there any packages which we expect to fail if it got updated?

@SamStaijen
Copy link
Copy Markdown
Member

alleen de lockfile is gechanged, wat is de commitcrowd best practice op package.json? doen we ^, ~, of hard version pinning? En wat willen we hier?

@SamStaijen
Copy link
Copy Markdown
Member

ik vind zelf denk ik ^ voor packages vaak fine

@SamStaijen
Copy link
Copy Markdown
Member

mits we de lockfile strict gebruiken in de pipeline (npm ci)

@SilasPeters
Copy link
Copy Markdown
Member Author

Oh right only the lock changed. I just did 'npm upgrade' or something that's all. I don't have a preference for ^ or ~

@SamStaijen
Copy link
Copy Markdown
Member

we should probably check wether or not there are major changes. I do not know if npm upgrade takes into account major changes, or just the minor and patch from ^ (or only the patch from ~)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants