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

Automate latest version of dependencies #25

Closed
blackfalcon opened this issue Mar 29, 2020 · 1 comment · Fixed by #26
Closed

Automate latest version of dependencies #25

blackfalcon opened this issue Mar 29, 2020 · 1 comment · Fixed by #26
Assignees
Labels
released Completed work has been released Type: Feature New Feature

Comments

@blackfalcon
Copy link
Member

General Support Request

Automate the package.temp file so that upon the new creation of a WC, this will always use the latest version of Auto dependencies.

Support request

When a new WC is created, the user must go through the process if updating dependencies. This may cause inconsistencies over time.

Possible Solution

Build into the generator JS the ability to reference the latest version number of any dependency and replace the content of the package.json file on generation.

Context

Having to manually manage dependencies is not practical.

@blackfalcon blackfalcon self-assigned this Mar 29, 2020
@blackfalcon blackfalcon added this to Backlog in Auro (general board) via automation Mar 29, 2020
@blackfalcon blackfalcon moved this from Backlog to Release #7 in Auro (general board) Mar 29, 2020
Auro (general board) automation moved this from Release #7 to Done/Deployed/Closed Apr 1, 2020
AuroDesignSystem pushed a commit that referenced this issue Apr 1, 2020
# [2.1.0](v2.0.0...v2.1.0) (2020-04-01)

### Features

* [#17](#17) remove gulp dependency ([bbece56](bbece56))
* [#24](#24) remove local token support ([598f6c2](598f6c2))
* [#25](#25) automate dependency package versions ([ee63b6a](ee63b6a))
* [#27](#27) custom namespace support ([ba605fc](ba605fc))
@AuroDesignSystem
Copy link
Collaborator

🎉 This issue has been resolved in version 2.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@AuroDesignSystem AuroDesignSystem added the released Completed work has been released label Apr 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released Completed work has been released Type: Feature New Feature
Projects
Auro (general board)
  
Done/Deployed/Closed
Development

Successfully merging a pull request may close this issue.

2 participants