chore(deps): update dependency tailwindcss to v4 #124
No reviewers
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
feeldata/feeldata.app!124
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/124/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
^3.4.3->^4.0.0Release Notes
tailwindlabs/tailwindcss (tailwindcss)
v4.1.1Compare Source
Fixed
@source inline(…)brace expansion (#17491)@importand body-less@layer(#17493)@tailwindcss/clidoes not contain an import forjiti(#17502)v4.1.0Compare Source
Added
details-contentvariant (#15319)inverted-colorsvariant (#11693)noscriptvariant (#11929, #17431)items-baseline-lastandself-baseline-lastutilities (#13888, #17476)pointer-none,pointer-coarse, andpointer-finevariants (#16946)any-pointer-none,any-pointer-coarse, andany-pointer-finevariants (#16941)user-validanduser-invalidvariants (#12370)wrap-anywhere,wrap-break-word, andwrap-normalutilities (#12128)@source inline(…)and@source not inline(…)(#17147)@source not "…"(#17255)text-shadow-*utilities (#17389)mask-*utilities (#17134)bg-{position,size}-*utilities for arbitrary values (#17432)shadow-*/<alpha>,inset-shadow-*/<alpha>,drop-shadow-*/<alpha>, andtext-shadow-*/<alpha>utilities to control shadow opacity (#17398, #17434)drop-shadow-<color>utilities (#17434)Fixed
@sourcedirectives (#17391)@tailwindcss/cli(#17255)contentrules in legacy JavaScript configuration (#17255)@("@​")md:…as@md:…in Razor files (#17427)--theme(…)function still resolves to the CSS variables when using legacy JS plugins (#17458)Changed
node_modulesby default (can be overridden by@source …rules) (#17255)@sourcerules that include file extensions or point insidenode_modules/folders no longer consider your.gitignorerules (#17255)bg-{left,right}-{top,bottom}in favor ofbg-{top,bottom}-{left,right}utilities (#17378)object-{left,right}-{top,bottom}in favor ofobject-{top,bottom}-{left,right}utilities (#17437)v4.0.17Compare Source
Fixed
v4.0.16Compare Source
Added
--value('…')and--modifier('…')(#17304)Fixed
(in Pug (#17320)@keyframesfor theme animations are emitted if they are referenced following a comma (#17352)Slimtemplates embedded in Ruby files (#17336)--spacing(--value(integer, number))is used (#17308)::-webkit-details-markerpseudo tomarkervariant (#17362)v4.0.15Compare Source
Fixed
-bg-conic-*utilities (#17174)border-[12px_4px]being interpreted as aborder-colorinstead of aborder-width(#17248)<template lang="…">in Vue files (#17252)--value(…)or--modifier(…)calls don't delete subsequent declarations (#17273)(in Slim (#17278)PluginUtilsfromtailwindcss/pluginfor compatibility with v3 (#17299)line-height: initialfrom Preflight (#15212)Changed
--theme(…)function now returns CSS variables from your theme variables unless used inside positions where CSS variables are invalid (e.g. inside@mediaqueries) (#17036)v4.0.14Compare Source
Fixed
${(#17142).character (#17153)v4.0.13Compare Source
Fixed
.nodeand.wasmfiles are not scanned for utilities (#17123)v4.0.12Compare Source
Fixed
url(…)rebasing in transitively imported CSS files (#16965)url(…)s in imported CSS files (#16965)}and{are properly extracted (#17001)razor/cshtmlpre-processing (#17027)v4.0.11Compare Source
Fixed
--are extracted correctly (#16972)[are extracted in Slim templating language (#16985)v4.0.10Compare Source
Added
col-<number>androw-<number>utilities forgrid-columnandgrid-row(#15183)Fixed
not-*does not remove:is(…)from variants (#16825)@keyframesare correctly emitted when using a prefix (#16850)@utilitydeclarations when@applyis used in nested rules (#16940)outline-hiddenbehaves likeoutline-noneoutside of forced colors mode (#16943)!importanton CSS variables again (#16873).svgfile with#or?in the filename (#16957)Changed
max-w-autoandmax-h-autoutilities as they generate invalid CSS (#16917)v4.0.9Compare Source
Fixed
.css(#16780)@reference "…"would sometimes omit keyframe animations (#16774)z-*!utilities are properly marked as!important(#16795)Changed
@reference "…"instead of duplicate CSS variable declarations (#16774)v4.0.8Compare Source
Added
@importwiththeme(…)options for stylesheets that contain more than just@themerules (#16514)Fixed
!importantto CSS variable declarations when using the important modifier (#16668).gitignorefile when using automatic source detection(#16631)translate-z-pxutilities once in compiled CSS (#16718)Changed
v4.0.7Compare Source
Fixed
tailwindcss/lib/util/flattenColorPalette.jsfor backward compatibility (#16411)_in suggested theme keys (#16433)--default-outline-widthcan be used to change theoutline-widthvalue of theoutlineutility (#16469)tailwindcss/pluginfor backward compatibility (#16505)@tailwindcss/oxideWindows builds (#16602)tailwindcssin@tailwindcss/*packages (#16623)darkModeJS config setting with block syntax converts to use@slot(#16507)tailwindcssand@tailwindcss/postcssare installed when upgrading (#16620)v4.0.6Compare Source
Fixed
blurtoblur-smwhen used with Next.js<Image placeholder="blur" />(#16405)v4.0.5Compare Source
Added
@theme staticoption for always including theme variables in compiled CSS (#16211)Fixed
console.logfrom@tailwindcss/vite(#16307)Changed
v4.0.4Compare Source
Fixed
null(#16210)containersJS theme key is added to the--container-*namespace (#16169)@keyframesare generated even if an--animation-*variable spans multiple lines (#16237)?commonjs-proxyflag (#16238)order-firstandorder-lastfor Firefox (#16266)NODE_PATHis respected when resolving JavaScript and CSS files (#16274)@variantinside a referenced stylesheet could cause a stack overflow (#16300)v4.0.3Compare Source
Fixed
@import url();(#16144)v4.0.2Compare Source
Fixed
grid-cols-*andgrid-rows-*utilities (#16020)@referenceor@variant(#16057)<style>blocks in HTML files (#16069)@keyframesin@theme reference(#16120)@variantwhen at the top-level of a stylesheet (#16129)v4.0.1Compare Source
Fixed
v4.0.0Compare Source
Added
@property, andcolor-mix().color-scheme,field-sizing, complex shadows,inert, and more.Start using Tailwind CSS v4.0 today by installing it in a new project, or playing with it directly in the browser on Tailwind Play.
For existing projects, we've published a comprehensive upgrade guide and built an automated upgrade tool to get you on the latest version as quickly and painlessly as possible.
For a deep-dive into everything that's new, check out the announcement post.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "* * * * *" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
op1st Pipelines as Code/on-pull-request-r49zj is running.
Starting Pipelinerun on-pull-request-r49zj in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-r49zj -fop1st Pipelines as Code/on-pull-request-r49zj has failed.
Task Statuses:
fetch-source-repository
unit-tests
build
Failure snippet:
task build has the status "Failed":op1st Pipelines as Code/on-pull-request-phf28 is running.
Starting Pipelinerun on-pull-request-phf28 in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-phf28 -fop1st Pipelines as Code/on-pull-request-phf28 has failed.
Task Statuses:
fetch-source-repository
build
unit-tests
Failure snippet:
task build has the status "Failed":op1st Pipelines as Code/on-pull-request-2blps is running.
Starting Pipelinerun on-pull-request-2blps in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-2blps -fop1st Pipelines as Code/on-pull-request-2blps has failed.
Task Statuses:
fetch-source-repository
unit-tests
build
Failure snippet:
task build has the status "Failed":op1st Pipelines as Code/on-pull-request-js8dk is running.
Starting Pipelinerun on-pull-request-js8dk in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-js8dk -fop1st Pipelines as Code/on-pull-request-f25ct is running.
Starting Pipelinerun on-pull-request-f25ct in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-f25ct -fop1st Pipelines as Code/on-pull-request-f25ct has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-jc498 is running.
Starting Pipelinerun on-pull-request-jc498 in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-jc498 -fop1st Pipelines as Code/on-pull-request-jc498 has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-vpm8m is running.
Starting Pipelinerun on-pull-request-vpm8m in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-vpm8m -fop1st Pipelines as Code/on-pull-request-vpm8m has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-99v29 is running.
Starting Pipelinerun on-pull-request-99v29 in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-99v29 -fop1st Pipelines as Code/on-pull-request-99v29 has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-jslt8 is running.
Starting Pipelinerun on-pull-request-jslt8 in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-jslt8 -fop1st Pipelines as Code/on-pull-request-jslt8 has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-k5tjn is running.
Starting Pipelinerun on-pull-request-k5tjn in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-k5tjn -fop1st Pipelines as Code/on-pull-request-k5tjn has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-m6q5g is running.
Starting Pipelinerun on-pull-request-m6q5g in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-m6q5g -fop1st Pipelines as Code/on-pull-request-m6q5g has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-r26jm is running.
Starting Pipelinerun on-pull-request-r26jm in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-r26jm -fop1st Pipelines as Code/on-pull-request-r26jm has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-6pv55 is running.
Starting Pipelinerun on-pull-request-6pv55 in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-6pv55 -fop1st Pipelines as Code/on-pull-request-6pv55 has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-nm6j8 is running.
Starting Pipelinerun on-pull-request-nm6j8 in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-nm6j8 -fop1st Pipelines as Code/on-pull-request-nm6j8 has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-c8w68 is running.
Starting Pipelinerun on-pull-request-c8w68 in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-c8w68 -fop1st Pipelines as Code/on-pull-request-c8w68 has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-vtpth is running.
Starting Pipelinerun on-pull-request-vtpth in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-vtpth -fop1st Pipelines as Code/on-pull-request-vtpth has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-c9v8j is running.
Starting Pipelinerun on-pull-request-c9v8j in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-c9v8j -fop1st Pipelines as Code/on-pull-request-c9v8j has failed.
Task Statuses:
fetch-source-repository
unit-tests
Failure snippet:
task unit-tests has the status "Failed":op1st Pipelines as Code/on-pull-request-2gn5f is running.
Starting Pipelinerun on-pull-request-2gn5f in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-2gn5f -fop1st Pipelines as Code/on-pull-request-2gn5f has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-qvlr5 is running.
Starting Pipelinerun on-pull-request-qvlr5 in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-qvlr5 -fop1st Pipelines as Code/on-pull-request-qvlr5 has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-nzf8b is running.
Starting Pipelinerun on-pull-request-nzf8b in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-nzf8b -fop1st Pipelines as Code/on-pull-request-nzf8b has failed.
Task Statuses:
fetch-source-repository
Failure snippet:
task fetch-source-repository has the status "Failed":{"level":"warn","ts":1741205646.7809155,"caller":"git/git.go:269","msg":"SSH credentials have been provided but the URL(\"https://codeberg.org/feeldata/feeldata.app\") is not a valid SSH URL. This warning can be safely ignored if the URL is for a public repo or you are using basic auth"} {"level":"error","ts":1741205701.0512311,"caller":"git/git.go:53","msg":"Error running git [fetch --recurse-submodules=yes --depth=1 origin --update-head-ok --force 88f09ffc87c38ddd30e17707c0c7b88a9f5a21b2]: exit status 128\nfatal: unable to access 'https://codeberg.org/feeldata/feeldata.app/': SSL: no alternative certificate subject name matches target host name 'codeberg.org'\n","stacktrace":"github.com/tektoncd/pipeline/pkg/git.run\n\tgithub.com/tektoncd/pipeline/pkg/git/git.go:53\ngithub.com/tektoncd/pipeline/pkg/git.Fetch\n\tgithub.com/tektoncd/pipeline/pkg/git/git.go:156\nmain.main\n\tgithub.com/tektoncd/pipeline/cmd/git-init/main.go:53\nruntime.main\n\truntime/proc.go:250"} {"level":"fatal","ts":1741205701.0513015,"caller":"git-init/main.go:54","msg":"Error fetching git repository: failed to fetch [88f09ffc87c38ddd30e17707c0c7b88a9f5a21b2]: exit status 128","stacktrace":"main.main\n\tgithub.com/tektoncd/pipeline/cmd/git-init/main.go:54\nruntime.main\n\truntime/proc.go:250"}op1st Pipelines as Code/on-pull-request-j422t is running.
Starting Pipelinerun on-pull-request-j422t in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the opc CLI with the following command:
opc pr logs -n feeldata-dev on-pull-request-j422t -fop1st Pipelines as Code/on-pull-request-j422t has failed.
Task Statuses:
fetch-source-repository
unit-tests
Failure snippet:
task unit-tests has the status "Failed":op1st Pipelines as Code has failed.
There was an error creating the PipelineRun: on-pull-request-
cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 9 comments in 10 minutes: rate limited
op1st Pipelines as Code/on-pull-request-g5h5n has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-xgjwc is running.
Starting Pipelinerun on-pull-request-xgjwc in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n feeldata-dev on-pull-request-xgjwc -fop1st Pipelines as Code/on-pull-request-n9hqz is running.
Starting Pipelinerun on-pull-request-n9hqz in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n feeldata-dev on-pull-request-n9hqz -fop1st Pipelines as Code/on-pull-request-n9hqz has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-z8w9v is running.
Starting Pipelinerun on-pull-request-z8w9v in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n feeldata-dev on-pull-request-z8w9v -fop1st Pipelines as Code/on-pull-request-69sks is running.
Starting Pipelinerun on-pull-request-69sks in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n feeldata-dev on-pull-request-69sks -fop1st Pipelines as Code/on-pull-request-28vff is running.
Starting Pipelinerun on-pull-request-28vff in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n feeldata-dev on-pull-request-28vff -fop1st Pipelines as Code/on-pull-request-28vff has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-wmbfc is running.
Starting Pipelinerun on-pull-request-wmbfc in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n feeldata-dev on-pull-request-wmbfc -fop1st Pipelines as Code/on-pull-request-wmbfc has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-tdqxn is running.
Starting Pipelinerun on-pull-request-tdqxn in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n feeldata-dev on-pull-request-tdqxn -fop1st Pipelines as Code/on-pull-request-tdqxn has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-9q96g is running.
Starting Pipelinerun on-pull-request-9q96g in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n feeldata-dev on-pull-request-9q96g -fop1st Pipelines as Code/on-pull-request-9q96g has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-qhfmk is running.
Starting Pipelinerun on-pull-request-qhfmk in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n feeldata-dev on-pull-request-qhfmk -fop1st Pipelines as Code/on-pull-request-qhfmk has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-26fbw is running.
Starting Pipelinerun on-pull-request-26fbw in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n feeldata-dev on-pull-request-26fbw -fop1st Pipelines as Code/on-pull-request-26fbw has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-m5sps is running.
Starting Pipelinerun on-pull-request-m5sps in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n feeldata-dev on-pull-request-m5sps -fop1st Pipelines as Code/on-pull-request-m5sps has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
op1st Pipelines as Code/on-pull-request-vsqzf is running.
Starting Pipelinerun on-pull-request-vsqzf in namespace feeldata-dev
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n feeldata-dev on-pull-request-vsqzf -fop1st Pipelines as Code/on-pull-request-vsqzf has successfully validated your commit.
Task Statuses:
fetch-source-repository
unit-tests
Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future
4.xreleases. But if you manually upgrade to4.xthen Renovate will re-enableminorandpatchupdates automatically.If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.
Pull request closed