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

Move to the npm ci in the Dockerfile #36

Closed
magicmatatjahu opened this issue Jan 17, 2022 · 10 comments
Closed

Move to the npm ci in the Dockerfile #36

magicmatatjahu opened this issue Jan 17, 2022 · 10 comments
Labels
bug Something isn't working stale

Comments

@magicmatatjahu
Copy link
Member

As in current Dockerfile we install dependencies by npm install due to problem described in the asyncapi/.github#123 issue. After resolving mentioned issue we should move from npm install to the npm ci.

@abhijeetjejurkar
Copy link
Contributor

Is this issue is resolved? and Remained to close?

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Jul 17, 2022
@github-actions github-actions bot removed the stale label Jul 29, 2022
@magicmatatjahu
Copy link
Member Author

@BOLT04
Copy link
Member

BOLT04 commented Nov 25, 2022

hi @magicmatatjahu, the PR asyncapi/.github#123 is necessary to be merged first right?
Could we do this change with a draft PR on this repo in the meantime, wdyt?

@magicmatatjahu
Copy link
Member Author

@BOLT04 Yeah, our workflow still try to install NodeJS projects with lockVersion: 1, so we have still problems described in the asyncapi/.github#123 issue.

Could we do this change with a draft PR on this repo in the meantime, wdyt?

Hmm 😅 Which PR? I don't see PR related to this problem in this repo. Could you clarify?

@BOLT04
Copy link
Member

BOLT04 commented Nov 25, 2022

ohh sorry, i meant if we could open a draft PR on this repo, changing to npm ci. It doesn't exist yet 😅 @magicmatatjahu

@magicmatatjahu
Copy link
Member Author

Aaa ok, sorry for misunderstanding! Yeah. you can create draft PR and check it :)

@BOLT04 BOLT04 added the gsoc This label shoudl be used for issues or discussions related to ideas for Google Summer of Code label Feb 9, 2023
@BOLT04 BOLT04 removed the gsoc This label shoudl be used for issues or discussions related to ideas for Google Summer of Code label Mar 9, 2023
@github-actions
Copy link

github-actions bot commented Jul 8, 2023

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Jul 8, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 6, 2023
@smoya
Copy link
Member

smoya commented Feb 4, 2024

Still relevant

@smoya smoya reopened this Feb 4, 2024
@github-actions github-actions bot removed the stale label Feb 5, 2024
Copy link

github-actions bot commented Jun 4, 2024

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Jun 4, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants