Clasp: npm package `forked-clasp` 2.4.0 open for testing

[PopGoesTheWza]

Pending folks from G Suite are available to update the npm @google/clasp package, I have published [email protected] with reflect this repos master branch.

npm uninstall -g @google/clasp && npm install -g forked-clasp
clasp --version
# should be 2.4.0 or more

This publish is not meant to live long but to provide access to the latest version.

[enuchi]

Thanks for this @PopGoesTheWza . Any guidance from the Google team on when the next version of @google/clasp can be released? Looks like it's been a year since the 2.3 release and there are some features in the master branch that would be great to be able to use. Thanks!

[grant]

Hi @PopGoesTheWza,

Can you please revert the following README changes:

• title: should clasp, not clasp (forked)
• badges
• notice: "This is an unofficial publish"

You may make a note of the latest release on forked-clasp in a note on the README, but please do not modify any other part of the readme as this is a Google repo. You're free to maintain this library and publish updates via the other npm module, but please keep the repo branding the same. –Thanks, Grant

[PopGoesTheWza]

@grant I must have made a mistake when merging branches on my forked repos. It was not intended to affect the upstream (google/clasp), especially for it has many changes you might not agree on.

I wish I could revert the last commit... but don't know how.

Please advise.

[grant]

Ok I'll figure it out and take care of it, don't worry. Have a good weekend

[PopGoesTheWza]

Hey @grant, I believe I correctly reverted unintentionnal merge.

Please double check and let me know if I was correct.

Also, if you have access to the repo Settings > Integration, can you check that TravisCI is correct?

[grant]

Thanks for reverting.
I don't have access to this repo's settings anymore and can't help here. :(

[PopGoesTheWza]

This is somewhat silly... no one for releases... no one to reconnect Travis...

[takanakahiko]

It's been a while.

While Google recommends the use of clasp in its various documents, clasp has become a product with security issues due to its inability to update dependencies.
Also, if it cannot be published by Googler, I think that the provision of releases should be automated by CI.
If you're not comfortable with PopGoesTheWza managing the project alone, I'm happy to go back to being a contributor, and in that case, we can set up a merge policy and correct each other's reviews to ensure reliability.

I know that clasp is a great product and I don't want it to go away. I hope you will take action.

P.S. @PopGoesTheWza I've also contacted Googler about this issue through another route. Let's wait for some more action from Googler.

[PopGoesTheWza]

@takanakahiko restoring TravisCI and improving/fixing tests would be a good start. Since these are not my strongest points, I have not even worked on this on my own fork.

[takanakahiko]

Travis CI will be difficult to manage in the future without Googler privileges, so it seems better to consider switching to the method using GitHub Actions, I will investigate.

[PopGoesTheWza]

@takanakahiko I can invite you on my fork if you think it might help.

[takanakahiko]

@PopGoesTheWza
I'm skeptical about using forked-clasp.
The work for forked-clasp is meaningless with the recovery of clasp (not forked).
I think it's better to wait for a reply from Googler before taking action.