Lock readme-generator-for-helm dependency #369

2022-10-13T04:45:15Z

justusbunsi commented

2022-10-13 04:45:15 +00:00

(Migrated from gitea.com)

With every push on main/master branch of that repository, the referenced
tarball is replaced, causing npm integrity checks to fail. Locking the used
reference to a specific commit hash is more reliable.

There is an open issue regarding publishing on NPM. As long as this is
not resolved, we would need to use this workaround to get updates.

(https://github.com/bitnami-labs/readme-generator-for-helm/issues/36)

Signed-off-by: justusbunsi sk.bunsenbrenner@gmail.com

With every push on main/master branch of that repository, the referenced tarball is replaced, causing npm integrity checks to fail. Locking the used reference to a specific commit hash is more reliable. There is an open issue regarding publishing on NPM. As long as this is not resolved, we would need to use this workaround to get updates. (https://github.com/bitnami-labs/readme-generator-for-helm/issues/36) Signed-off-by: justusbunsi <sk.bunsenbrenner@gmail.com>

pat-s (Migrated from gitea.com) approved these changes 2022-10-13 07:45:43 +00:00

pat-s (Migrated from gitea.com) left a comment

Cheap workaround for the moment ?
How do we make sure to not forget about the fixed hash?

Should we look for other README generators?

Cheap workaround for the moment ? How do we make sure to not forget about the fixed hash? Should we look for other README generators?

techknowlogick (Migrated from gitea.com) approved these changes 2022-10-13 16:16:33 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: lunny/helm-chart#369