-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
Update versions in #beautifulComments, #documentBrowser and #welcomeBrowser for BaselineOfPharo for Pharo 11 to ‘v1.0.1’, ‘v1.0.3’ and ‘v1.0.2’ #17427
Conversation
Tx Kris |
I'm trying to create a tag but with the GH UI so far I failed. I will check if I can do that on the command line. |
I pushed the two tags. |
So now rechecking the build |
Looks like the there is a problem:
|
Ah but I'm also confused because it should be for Pharo 11 so I do not know how this build can show us anything. |
Thanks! There was no new build though because Jenkins didn’t process the ‘REMOVED event’ before you had reopened the pull request, see the following from the ‘Multibranch Pipeline Events’ log, and the example from the log I gave in pull request #16172:
|
I’m guessing the error in build 2 is due to BaselineOfBeautifulComments referring to ‘master’ for Microdown. I added commit b6d150f and opened a pull request for that: BeautifulComments pull request #49. |
Hi @Rinzwind thanks so much for the PR, I will see what is happening to help you with this |
I do not see any v1.0.1 tag in Beautiful comments. https://github.com/pillar-markup/BeautifulComments/tags
|
I just released it. https://github.com/pillar-markup/BeautifulComments/releases/tag/v1.0.1 I'll restart the CI |
Ok, thanks! I’m afraid I don’t understand the error on Windows in build 6, I’ll try starting another one. |
Build 7 seems to have the same error(s) on Windows:
|
This PR allows the image to build even of the windows tests are broken. I'll merge |
This pull request updates the versions in
#documentBrowser
and#welcomeBrowser
for BaselineOfPharo for Pharo 11 to ‘v1.0.3’ and ‘v1.0.2’ respectively. The tags need to be added first, I cannot do that; for NewTools-DocumentBrowser, ‘v1.0.3’ should refer to commit 7d3996762a13, and for NewTools-WelcomeBrowser, ‘v1.0.2’ should refer to commit ed5c5339466e.