upload the zip file on Ghost (3.1.1) manually and it’s all good.
So, I’m sure the theme itself is well coded. It passes the gscan test as well.
Error in the CI
But in the CI, the build fails here:
Error: Request body larger than maxBodyLength limit
at RedirectableRequest.module.exports.549.RedirectableRequest.write (/home/runner/work/_actions/TryGhost/action-deploy-theme/v1.2.0/dist/index.js:7813:24)
at FormData.ondata (internal/streams/legacy.js:17:31)
at FormData.emit (events.js:210:5)
at FormData.module.exports.547.CombinedStream.write (/home/runner/work/_actions/TryGhost/action-deploy-theme/v1.2.0/dist/index.js:7639:8)
at DelayedStream.ondata (internal/streams/legacy.js:17:31)
at DelayedStream.emit (events.js:210:5)
at DelayedStream.module.exports.152.DelayedStream._handleEmit (/home/runner/work/_actions/TryGhost/action-deploy-theme/v1.2.0/dist/index.js:2378:15)
at ReadStream.source.emit (/home/runner/work/_actions/TryGhost/action-deploy-theme/v1.2.0/dist/index.js:2325:19)
at addChunk (_stream_readable.js:309:12)
at readableAddChunk (_stream_readable.js:290:11) {
isAxiosError: true,
toJSON: [Function]
}
##[error]Node run failed with exit code 1
This is foreign to me and I don’t understand why I’m getting this error.
It seems like you’re zipping both your development data and dist data ~ the image referenced in the deploy probably doesn’t have a “build” step
However, there might be an issue in the Admin SDK that borks when payloads > 10 MB exist. I haven’t fully checked, but it looks like the default maxBodyLength value is 10 MB in axios['s dependency], the request lib used by the sdk.
If your dist folder is less than 10MB, everything should be fine
As of now, it doesn’t support providing a zip file (there’s a somewhat-related issue).
I’ve made the necessary changes in master of my fork (I haven’t used GA as a publisher so I didn’t realize there’s an additional publishing step involved in making it generally available ). If you can figure out how to make it work with the uses flag, feel free to
Humm, the logs are the same. We can see the that CI is compiling the /assets, node_modules, etc.
If you ask me, it does not make sense to see all these files being processed when we specific file: dist.zip
Run vikaspotluri123/action-deploy-theme@master
with:
api-url: ***
api-key: ***
file: dist.zip
Error: Request body larger than maxBodyLength limit
at RedirectableRequest.module.exports.549.RedirectableRequest.write (/home/runner/work/_actions/vikaspotluri123/action-deploy-theme/master/dist/index.js:7821:24)
at FormData.ondata (internal/streams/legacy.js:17:31)
at FormData.emit (events.js:210:5)
at FormData.module.exports.547.CombinedStream.write (/home/runner/work/_actions/vikaspotluri123/action-deploy-theme/master/dist/index.js:7647:8)
at DelayedStream.ondata (internal/streams/legacy.js:17:31)
at DelayedStream.emit (events.js:210:5)
at DelayedStream.module.exports.152.DelayedStream._handleEmit (/home/runner/work/_actions/vikaspotluri123/action-deploy-theme/master/dist/index.js:2386:15)
at ReadStream.source.emit (/home/runner/work/_actions/vikaspotluri123/action-deploy-theme/master/dist/index.js:2333:19)
at addChunk (_stream_readable.js:309:12)
at readableAddChunk (_stream_readable.js:290:11) {
isAxiosError: true,
toJSON: [Function]
}
This masking is necessary to avoid private secrets that give complete admin access to your site leaking through log files or being shared such as what you’ve been doing here ;-) Secret masking is a standard security practice and is done automatically by GitHub when it creates workflow logs.