Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump puppeteer support to 17.0 #43

Merged
merged 6 commits into from
Sep 12, 2022
Merged

Conversation

vladfrangu
Copy link
Member

@vladfrangu vladfrangu commented Aug 22, 2022

@vladfrangu vladfrangu changed the title deps: bump puppeteer support to 15.1 chore(deps): bump puppeteer support to 15.1 Aug 22, 2022
@vladfrangu vladfrangu changed the title chore(deps): bump puppeteer support to 15.1 chore(deps): bump puppeteer support to 17.1 Sep 5, 2022
@vladfrangu vladfrangu changed the title chore(deps): bump puppeteer support to 17.1 chore(deps): bump puppeteer support to 17.0 Sep 5, 2022
@B4nan
Copy link
Member

B4nan commented Sep 10, 2022

we should merge this before shipping new version. i dont think the CI will get fixed itself somehow :]

@vladfrangu
Copy link
Member Author

CI won't fix unless we release crawlee first @B4nan so yeah, maybe we should just merge it now

@B4nan
Copy link
Member

B4nan commented Sep 10, 2022

Oh I see, I dont want to breake the build. We can use npm i -f if its just about peer deps? Or any other issues?

I would still like to explore conditional builds so we can depend on beta crawlee for dev versions and have the stable there for stable releases only. I feel like we will be falling into this regularly.

@vladfrangu
Copy link
Member Author

Hmm, the CI is currently failing because the lock file is out of sync, let me fix that

@B4nan B4nan merged commit 038b753 into master Sep 12, 2022
@B4nan B4nan deleted the deps/puppeteer-15.1 branch September 12, 2022 09:50
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.

None yet

2 participants