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.

Sign up for GitHub

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

Jump to bottom

Drop node 8 #231

Closed
onderceylan opened this issue Apr 13, 2020 · 1 comment · Fixed by #230
Closed

Drop node 8 #231

onderceylan opened this issue Apr 13, 2020 · 1 comment · Fixed by #230
Assignees
@onderceylan
Labels
enhancement Code improvement, refactor released

Comments

@onderceylan
Copy link
Collaborator

Drop node 8 as it reached it's EOL
@onderceylan onderceylan added the feature request New feature or request label Apr 13, 2020
@onderceylan onderceylan self-assigned this Apr 13, 2020
onderceylan added a commit that referenced this issue Apr 13, 2020
@onderceylan
feat(node): drop node 8 support due to its EOL
fa856c8 
Dropped node 8 support due to its EOL

BREAKING CHANGE: Users with node v8 will not be actively supported.

fix #231
onderceylan added a commit that referenced this issue Apr 14, 2020
@onderceylan
feat(node): drop node 8 support due to its EOL
b0aac46 
Dropped node 8 support due to its EOL

BREAKING CHANGE: Users with node v8 will not be actively supported.

fix #231
@onderceylan onderceylan added enhancement Code improvement, refactor and removed feature request New feature or request labels Apr 17, 2020
onderceylan added a commit that referenced this issue May 13, 2020
@onderceylan
feat(node): drop node 8 support due to its EOL
345e83f 
Dropped node 8 support due to its EOL

BREAKING CHANGE: Users with node v8 will not be actively supported.

fix #231
onderceylan added a commit that referenced this issue May 14, 2020
@onderceylan
feat(node): drop node 8 support due to its EOL
df91a1f 
Dropped node 8 support due to its EOL

BREAKING CHANGE: Users with node v8 will not be actively supported.

fix #231
@onderceylan onderceylan mentioned this issue May 14, 2020
Merged
onderceylan added a commit that referenced this issue May 15, 2020
@onderceylan
feat(node): drop node 8 support due to its EOL
030569b 
Dropped node 8 support due to its EOL

BREAKING CHANGE: Users with node v8 will not be actively supported.

fix #231
onderceylan pushed a commit that referenced this issue May 15, 2020
@semantic-release-bot
chore(release): 3.0.0 [skip ci]
3881046 
# [3.0.0](v2.3.0...v3.0.0) (2020-05-15)

### Bug Fixes

* **cli:** fixed conflicting -h option ([3d4f04c](3d4f04c)), closes [#263](#263)

### Features

* **main:** added dark mode media query support for html inputs ([c5d2e0d](c5d2e0d)), closes [#227](#227)
* **main:** added stricter chrome launch args set ([bdfbef4](bdfbef4)), closes [#229](#229)
* **main:** exported appleDeviceSpecsForLaunchImages from module API ([dac56d4](dac56d4)), closes [#248](#248)
* **main:** switched to JPG as default output type ([bb5cfec](bb5cfec)), closes [#278](#278)
* **meta:** added xhtml option to introduce self-closing meta tags ([0dea81a](0dea81a)), closes [#192](#192)
* **node:** drop node 8 support due to its EOL ([030569b](030569b)), closes [#231](#231)

### BREAKING CHANGES

* **main:** Due to the large carbon footprint that PNG assets create, switched over using JPG
output with compression by default.
* **cli:** -h path override usage is dropped. It's replaced with -v shorthand.
* **node:** Users with node v8 will not be actively supported.
@onderceylan
Copy link
Collaborator Author

🎉 This issue has been resolved in version 3.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

@onderceylan onderceylan

Labels
enhancement Code improvement, refactor released
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Next features elegantapp/pwa-asset-generator
1 participant
@onderceylan