Closed black7375 closed 1 month ago
Latest commit: 361e0778f485330e469f48121e8efa2a4bc83e82
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
Triggered from https://github.com/mincho-js/mincho/pull/80 by @​black7375.
Checking if we can fast forward main
(1470f5b06ed34e867336fdba40262ff652a429c7) to publish-test
(361e0778f485330e469f48121e8efa2a4bc83e82).
Target branch (main
):
commit 1470f5b06ed34e867336fdba40262ff652a429c7 (HEAD -> main, origin/main, origin/HEAD)
Author: alstjr7375 <alstjr7375@daum.net>
Date: Sat Aug 17 21:04:27 2024 +0900
Fix: Try to publish without `build:release`
Pull request (publish-test
):
commit 361e0778f485330e469f48121e8efa2a4bc83e82 (pull_request/publish-test)
Author: alstjr7375 <alstjr7375@daum.net>
Date: Sat Aug 17 21:44:46 2024 +0900
Chore: Revert #79 and Show logs on failure
It is possible to fast forward main
(1470f5b06ed34e867336fdba40262ff652a429c7) to publish-test
(361e0778f485330e469f48121e8efa2a4bc83e82). If you have write access to the target repository, you can add a comment with /fast-forward
to fast forward main
to publish-test
.
This update enhances the project by improving debugging capabilities in the GitHub Actions workflow and refining the build process before publishing packages. A new job step displays log files on failure, facilitating quicker issue diagnosis. Additionally, the publish
script in the package.json
file is updated to ensure a more comprehensive build, and the @mincho-js/debug-log
package is incremented to version 1.0.3
with a new publishing configuration.
File | Change Summary |
---|---|
.github/workflows/fast-forward.yml |
Added a "Show log on failure" step to display npm cache logs when previous steps fail. |
package.json |
Updated the publish script to run build:release before changeset publish . |
packages/debug-log/CHANGELOG.md |
Introduced version entry 1.0.3 , documenting a patch change for the re-publication of a test. |
packages/debug-log/package.json |
Incremented version from 1.0.2 to 1.0.3 and added publishConfig specifying a new directory. |
🐇 In the log’s whisper, secrets unfold,
When failures arise, our stories are told.
With builds that are sturdy, we publish with glee,
A hop and a skip, from bugs we are free!
Let’s celebrate progress, both big and small,
In the garden of code, we flourish for all! 🌼
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Triggered from https://github.com/mincho-js/mincho/pull/80#issuecomment-2294850537 by @​coderabbitai[bot].
Trying to fast forward main
(1470f5b06ed34e867336fdba40262ff652a429c7) to publish-test
(361e0778f485330e469f48121e8efa2a4bc83e82).
Target branch (main
):
commit 1470f5b06ed34e867336fdba40262ff652a429c7 (HEAD -> main, origin/main, origin/HEAD)
Author: alstjr7375 <alstjr7375@daum.net>
Date: Sat Aug 17 21:04:27 2024 +0900
Fix: Try to publish without `build:release`
Pull request (publish-test
):
commit 361e0778f485330e469f48121e8efa2a4bc83e82 (pull_request/publish-test)
Author: alstjr7375 <alstjr7375@daum.net>
Date: Sat Aug 17 21:44:46 2024 +0900
Chore: Revert #79 and Show logs on failure
curl: (3) bad range in URL position 74: https://api.github.com/repos/mincho-js/mincho/collaborators/coderabbitai[bot]/permission ^
Triggered from https://github.com/mincho-js/mincho/pull/80#issuecomment-2294850537 by @​coderabbitai[bot].
Trying to fast forward main
(1470f5b06ed34e867336fdba40262ff652a429c7) to publish-test
(361e0778f485330e469f48121e8efa2a4bc83e82).
Target branch (main
):
commit 1470f5b06ed34e867336fdba40262ff652a429c7 (HEAD -> main, origin/main, origin/HEAD)
Author: alstjr7375 <alstjr7375@daum.net>
Date: Sat Aug 17 21:04:27 2024 +0900
Fix: Try to publish without `build:release`
Pull request (publish-test
):
commit 361e0778f485330e469f48121e8efa2a4bc83e82 (pull_request/publish-test)
Author: alstjr7375 <alstjr7375@daum.net>
Date: Sat Aug 17 21:44:46 2024 +0900
Chore: Revert #79 and Show logs on failure
curl: (3) bad range in URL position 74: https://api.github.com/repos/mincho-js/mincho/collaborators/coderabbitai[bot]/permission ^
/fast-forward
Triggered from https://github.com/mincho-js/mincho/pull/80#issuecomment-2294851379 by @​black7375.
Trying to fast forward main
(1470f5b06ed34e867336fdba40262ff652a429c7) to publish-test
(361e0778f485330e469f48121e8efa2a4bc83e82).
Target branch (main
):
commit 1470f5b06ed34e867336fdba40262ff652a429c7 (HEAD -> main, origin/main, origin/HEAD)
Author: alstjr7375 <alstjr7375@daum.net>
Date: Sat Aug 17 21:04:27 2024 +0900
Fix: Try to publish without `build:release`
Pull request (publish-test
):
commit 361e0778f485330e469f48121e8efa2a4bc83e82 (pull_request/publish-test)
Author: alstjr7375 <alstjr7375@daum.net>
Date: Sat Aug 17 21:44:46 2024 +0900
Chore: Revert #79 and Show logs on failure
Fast forwarding main
(1470f5b06ed34e867336fdba40262ff652a429c7) to publish-test
(361e0778f485330e469f48121e8efa2a4bc83e82).
$ git push origin 361e0778f485330e469f48121e8efa2a4bc83e82:main
To https://github.com/mincho-js/mincho.git
1470f5b..361e077 361e0778f485330e469f48121e8efa2a4bc83e82 -> main
Description
Now that
^workspace
is included, it's clear that we need to go back.It also includes a step to output a log when the action fails so you know what happened.
Related Issue
79
Summary by CodeRabbit
New Features
Bug Fixes
1.0.3
of the@mincho-js/debug-log
package includes re-publication of a test.Documentation
@mincho-js/debug-log
package.Additional context
Checklist