content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
meaning ### "unsuccessful cred copy" Warning This message has the following format: > `warning: unsuccessful cred copy: ".docker" from "/tekton/creds" to > "/tekton/home": unable to open destination: open > /tekton/home/.docker/config.json: permission denied` The precise credential and paths mentioned can vary. This me... | https://github.com/tektoncd/pipeline/blob/main//docs/auth.md | main | tekton | [
-0.06786882132291794,
0.08132151514291763,
-0.029982639476656914,
-0.02619648166000843,
0.015351304784417152,
-0.05629805102944374,
0.046990569680929184,
0.024682624265551567,
0.0358932688832283,
-0.00429553771391511,
-0.014387846924364567,
-0.09734473377466202,
0.07472287863492966,
0.0726... | -0.010423 |
2. There are an extremely limited set of supported credential types. 3. Tasks with Steps that have different UIDs can break if multiple Steps are trying to share access to the same credentials. 4. Tasks with Steps that have different UIDs can log more warning messages, creating more noise in TaskRun logs. Again this is... | https://github.com/tektoncd/pipeline/blob/main//docs/auth.md | main | tekton | [
-0.05985657870769501,
0.04348897933959961,
0.011980914510786533,
-0.05097672715783119,
-0.032108061015605927,
-0.024782773107290268,
-0.008291851729154587,
-0.003072522347792983,
0.08900772035121918,
0.0343543104827404,
-0.06453894078731537,
-0.10565293580293655,
0.0711204782128334,
0.0626... | 0.033301 |
# Matrix - [Overview](#overview) - [Configuring a Matrix](#configuring-a-matrix) - [Generating Combinations](#generating-combinations) - [Explicit Combinations](#explicit-combinations) - [Concurrency Control](#concurrency-control) - [Parameters](#parameters) - [Parameters in Matrix.Params](#parameters-in-matrixparams-1... | https://github.com/tektoncd/pipeline/blob/main//docs/matrix.md | main | tekton | [
-0.025484833866357803,
0.02061433158814907,
-0.14389286935329437,
0.04795698821544647,
-0.08653068542480469,
0.01610654592514038,
-0.02035563439130783,
-0.048892199993133545,
-0.044167209416627884,
0.004452587105333805,
0.020791077986359596,
-0.037262409925460815,
0.04598737880587578,
-0.0... | 0.013258 |
unique name of each `matrix` instance such that it is easier to distinguish all the instances based on their inputs. ```yaml pipelineSpec: tasks: - name: platforms-and-browsers displayName: "Platforms and Browsers: $(params.platform) and $(params.browser)" matrix: params: - name: platform value: - linux - mac - windows... | https://github.com/tektoncd/pipeline/blob/main//docs/matrix.md | main | tekton | [
-0.03071853518486023,
0.007564594969153404,
-0.0879359245300293,
-0.01677393727004528,
-0.04196159914135933,
-0.03982357680797577,
-0.010490461252629757,
-0.007332558743655682,
0.07897136360406876,
-0.056770555675029755,
-0.0027764090336859226,
-0.06707027554512024,
0.0007812061812728643,
... | 0.01521 |
Parameters in Matrix.Include.Params `Matrix.Include.Params` takes string replacements from `Parameters` of type String, Array or Object. ```yaml tasks: ... - name: task-4 taskRef: name: task-4 matrix: include: - name: foo-bar-rad params: - name: foo value: $(params.foo) # string replacement from string param - name: ba... | https://github.com/tektoncd/pipeline/blob/main//docs/matrix.md | main | tekton | [
-0.029034774750471115,
-0.0013582364190369844,
-0.08174704015254974,
0.031433094292879105,
-0.037519920617341995,
-0.05730815231800079,
-0.010752755217254162,
-0.028179679065942764,
0.026327969506382942,
-0.007844571024179459,
0.005141114350408316,
0.006225268356502056,
0.012747065164148808,... | 0.028098 |
during reconciliation, in which the whole `array` of `Results` can be consumed by another `pipelineTask` using the star notion [\*]. Note: A known limitation is not being able to consume a singular result or specific combinations of results produced by a previous fanned out `PipelineTask`. | Result Type in `taskRef` or... | https://github.com/tektoncd/pipeline/blob/main//docs/matrix.md | main | tekton | [
-0.042240217328071594,
0.03210131824016571,
-0.06414234638214111,
0.02625790610909462,
-0.08389970660209656,
-0.010228920727968216,
0.01527357567101717,
-0.035882942378520966,
0.004632089752703905,
-0.03291113302111626,
-0.07678377628326416,
-0.032309968024492264,
0.014485986903309822,
-0.... | 0.060455 |
to the original `matrix` combinations that include `"GOARCH": "linux/s390x"`: ```json! { "GOARCH": "linux/s390x", "version": "go1.17", "package": "path/to/common/package/", \*\*"flags": "-cover -v"\*\* } { "GOARCH": "linux/s390x", "version": "go1.18.1", "package": "path/to/common/package/", \*\*"flags": "-cover -v"\*\*... | https://github.com/tektoncd/pipeline/blob/main//docs/matrix.md | main | tekton | [
-0.04533553868532181,
0.011274851858615875,
-0.09584368765354156,
-0.04363028705120087,
0.038315966725349426,
0.016384931281208992,
0.01620173640549183,
-0.04874305799603462,
-0.024278759956359863,
-0.006837695837020874,
0.10297054797410965,
-0.01639016717672348,
-0.00043183285742998123,
0... | 0.054539 |
platform-browsers startTime: "2022-06-23T23:01:11Z" completionTime: "2022-06-23T23:01:20Z" conditions: - lastTransitionTime: "2022-06-23T23:01:20Z" message: 'Tasks Completed: 1 (Failed: 0, Cancelled 0), Skipped: 0' reason: Succeeded status: "True" type: Succeeded childReferences: - apiVersion: tekton.dev/v1beta1 kind: ... | https://github.com/tektoncd/pipeline/blob/main//docs/matrix.md | main | tekton | [
-0.028313186019659042,
0.02690509706735611,
-0.07194232940673828,
-0.025570763275027275,
0.059736739844083786,
-0.06544546037912369,
-0.04729052260518074,
-0.011875873431563377,
0.00586897786706686,
0.0052086664363741875,
-0.003724695648998022,
-0.08448244631290436,
-0.025506649166345596,
... | 0.028327 |
# Labels and Annotations Tekton allows you to use custom [Kubernetes Labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) to easily mark Tekton entities belonging to the same conceptual execution chain. Tekton also automatically adds select labels to more easily identify resource relations... | https://github.com/tektoncd/pipeline/blob/main//docs/labels.md | main | tekton | [
-0.007743550930172205,
0.03065839223563671,
-0.048317957669496536,
-0.015309398993849754,
-0.013406827114522457,
0.01532074250280857,
0.06097318232059479,
-0.0015340681420639157,
0.08338739722967148,
-0.030101049691438675,
-0.011456823907792568,
-0.13913126289844513,
-0.023079730570316315,
... | 0.200912 |
The same as above applies. | https://github.com/tektoncd/pipeline/blob/main//docs/labels.md | main | tekton | [
-0.025573987513780594,
0.0067045544274151325,
-0.00006630702409893274,
-0.015810701996088028,
0.04912123829126358,
0.000798138149548322,
-0.002593066543340683,
-0.011452725157141685,
0.0347382090985775,
-0.016067704185843468,
0.1081908568739891,
0.009331966750323772,
0.06735333055257797,
-... | 0.087498 |
# Resolver Reference Writing a resolver is made easier with the `github.com/tektoncd/pipeline/pkg/resolution/resolver/framework` package. This package exposes a number of interfaces that let your code control what kind of behaviour it should have when running. To get started really quickly see the [resolver template](.... | https://github.com/tektoncd/pipeline/blob/main//docs/resolver-reference.md | main | tekton | [
-0.06551357358694077,
0.013223990797996521,
-0.03013996221125126,
-0.005728984251618385,
-0.06986487656831741,
-0.061937879770994186,
-0.041269056499004364,
0.12342119961977005,
-0.019740162417292595,
0.033355046063661575,
-0.053921326994895935,
0.0062637608498334885,
-0.005162647459656,
0... | -0.017165 |
zombie requests remaining in an incomplete state forever. | Method to Implement | Description | |---------------------|-------------| | GetResolutionTimeout | Return a custom timeout duration from this method to control how long a resolution request to this resolver may take. | | https://github.com/tektoncd/pipeline/blob/main//docs/resolver-reference.md | main | tekton | [
-0.07432902604341507,
0.08331712335348129,
-0.019329508766531944,
-0.009425332769751549,
-0.058528099209070206,
-0.06621699780225754,
-0.08880025148391724,
0.011759706772863865,
-0.006680104415863752,
0.06272637844085693,
-0.02509237825870514,
0.007238138932734728,
-0.006883326917886734,
-... | 0.072128 |
# Pipeline Controller Metrics The following pipeline metrics are available at `controller-service` on port `9090`. We expose several kinds of exporters, including Prometheus, Google Stackdriver, and many others. You can set them up using [observability configuration](../config/config-observability.yaml). | Name | Type ... | https://github.com/tektoncd/pipeline/blob/main//docs/metrics.md | main | tekton | [
-0.059980496764183044,
-0.04962906613945961,
-0.09214364737272263,
-0.01582220382988453,
-0.025593779981136322,
-0.0753844752907753,
-0.10282405465841293,
0.02455250546336174,
-0.060938794165849686,
-0.040466148406267166,
0.028164109215140343,
-0.07077928632497787,
-0.014666672796010971,
-... | 0.020729 |
that appropriate values have been applied in response to configmap changes, use the following commands: ```shell kubectl port-forward -n tekton-pipelines service/tekton-pipelines-controller 9090 ``` And then check that changes have been applied to metrics coming from [http://127.0.0.1:9090/metrics](http://127.0.0.1:909... | https://github.com/tektoncd/pipeline/blob/main//docs/metrics.md | main | tekton | [
0.02102782018482685,
0.01752849854528904,
-0.006647020578384399,
-0.04794681444764137,
-0.05886435881257057,
-0.06056345999240875,
-0.036189258098602295,
0.01480091456323862,
0.03979286551475525,
0.0012964061461389065,
0.0016526899999007583,
-0.15454807877540588,
-0.03890012204647064,
-0.0... | 0.095649 |
# HTTP Resolver This resolver responds to type `http`. ## Parameters | Param Name | Description | Example Value | | | -------------------------- | -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------... | https://github.com/tektoncd/pipeline/blob/main//docs/http-resolver.md | main | tekton | [
-0.06057635322213173,
0.05158521234989166,
0.023582331836223602,
0.0068835061974823475,
-0.13012154400348663,
-0.07038689404726028,
-0.052115149796009064,
0.03992098569869995,
0.005046837497502565,
-0.017178446054458618,
-0.04033268988132477,
-0.06290440261363983,
0.021866651251912117,
-0.... | 0.02762 |
⚠️ This is a work in progress: SPIRE support is not yet functional TaskRun result attestations is currently an alpha experimental feature. Currently all that is implemented is support for configuring Tekton to connect to SPIRE. See TEP-0089 for details on the overall design and feature set. This being a large feature, ... | https://github.com/tektoncd/pipeline/blob/main//docs/spire.md | main | tekton | [
-0.07234732806682587,
0.027023782953619957,
-0.026884837076067924,
0.04244527965784073,
0.0136263994500041,
-0.024307100102305412,
-0.01614558696746826,
0.009091729298233986,
-0.07682078331708908,
0.06286008656024933,
-0.08641763776540756,
-0.05341678857803345,
0.0055261109955608845,
0.073... | 0.031574 |
be used. 1. Register the SPIRE workload entry for Tekton with the "Admin" flag, which will allow the Tekton controller to communicate with the SPIRE server to manage the TaskRun identities dynamically. ``` # This example is assuming use of the above SPIRE deployment # Example where trust domain is "example.org" and clu... | https://github.com/tektoncd/pipeline/blob/main//docs/spire.md | main | tekton | [
-0.020618759095668793,
0.006691077258437872,
-0.08531377464532852,
0.022769110277295113,
-0.06363659352064133,
-0.005860086530447006,
0.023492468520998955,
0.023014908656477928,
0.031734827905893326,
0.07035714387893677,
-0.05089274048805237,
-0.11195917427539825,
0.009085520170629025,
-0.... | 0.10712 |
# StepActions - [Overview](#overview) - [Configuring a StepAction](#configuring-a-stepaction) - [Declaring Parameters](#declaring-parameters) - [Passing Params to StepAction](#passing-params-to-stepaction) - [Emitting Results](#emitting-results) - [Fetching Emitted Results from StepActions](#fetching-emitted-results-fr... | https://github.com/tektoncd/pipeline/blob/main//docs/stepactions.md | main | tekton | [
-0.06986947357654572,
0.00007163229747675359,
-0.06351723521947861,
0.027558915317058563,
0.0019699425902217627,
0.031045343726873398,
0.05428773909807205,
0.036946460604667664,
-0.03613753989338875,
0.005770307499915361,
0.04111161455512047,
-0.033893126994371414,
0.08274272084236145,
-0.... | 0.078627 |
it with `params`, just like how a `TaskRun` provides params to the underlying `Task`. ```yaml apiVersion: tekton.dev/v1 kind: Task metadata: name: step-action spec: params: - name: param-for-step-action description: "this is a param that the step action needs." steps: - name: action-runner ref: name: step-action params... | https://github.com/tektoncd/pipeline/blob/main//docs/stepactions.md | main | tekton | [
-0.11752732843160629,
0.013446299359202385,
-0.02665392868220806,
0.024685751646757126,
0.003042003372684121,
0.005594360642135143,
-0.02325095422565937,
0.001893284497782588,
0.025729410350322723,
0.011699464172124863,
-0.01485730055719614,
-0.031130652874708176,
0.007838686928153038,
0.0... | 0.097784 |
- name: digest description: "digest of the image" value: $(steps.kaniko.results.digest) steps: - name: git-clone ref: name: clone-step-action - name: kaniko ref: name: kaniko-step-action ``` #### Passing Results between Steps `StepResults` (i.e. results written to `$(step.results..path)`, NOT `$(results..path)`) can be... | https://github.com/tektoncd/pipeline/blob/main//docs/stepactions.md | main | tekton | [
0.015070358291268349,
0.05355724319815636,
0.01919238083064556,
0.05130196735262871,
-0.004929660353809595,
-0.017010951414704323,
-0.01183084212243557,
0.0440664179623127,
0.06429190933704376,
-0.04016325995326042,
0.00033190587419085205,
-0.02696242928504944,
-0.01922374591231346,
-0.007... | 0.044322 |
kind: StepAction metadata: name: myStep spec: description: my step params: ... volumeMounts: ... image: ... script: ... ``` ### Referencing a StepAction `StepActions` can be referenced from the `Step` using the `ref` field, as follows: ```yaml apiVersion: tekton.dev/v1 kind: TaskRun metadata: name: step-action-run spec... | https://github.com/tektoncd/pipeline/blob/main//docs/stepactions.md | main | tekton | [
-0.05329617112874985,
-0.01019530650228262,
-0.01026933267712593,
0.002513458486646414,
0.02294878475368023,
0.009673943743109703,
-0.020308805629611015,
0.04763690009713173,
0.04230634123086929,
0.0221407450735569,
-0.0118250148370862,
-0.050264373421669006,
-0.005740400869399309,
0.01280... | 0.061813 |
# How to write a Resolver This how-to will outline the steps a developer needs to take when creating a new (very basic) Resolver. Rather than focus on support for a particular version control system or cloud platform this Resolver will simply respond with some hard-coded YAML. If you aren't yet familiar with the meanin... | https://github.com/tektoncd/pipeline/blob/main//docs/how-to-write-a-resolver.md | main | tekton | [
-0.08285665512084961,
0.014627284370362759,
0.045892298221588135,
-0.03538982570171356,
-0.06656445562839508,
-0.07073195278644562,
-0.0817052572965622,
0.04577632248401642,
0.06164557859301567,
0.0697239562869072,
-0.08690883964300156,
-0.035610489547252655,
-0.00879049301147461,
-0.04829... | 0.127902 |
"knative.dev/pkg/injection/sharedmain" ) func main() { sharedmain.Main("controller", framework.NewController(context.Background(), &resolver{}), ) } type resolver struct {} ``` {{% /tab %}} {{% /tabs %}} This won't compile yet but you can download the dependencies by running: ```bash # Depending on your go version you ... | https://github.com/tektoncd/pipeline/blob/main//docs/how-to-write-a-resolver.md | main | tekton | [
-0.0244522076100111,
-0.0037868984509259462,
-0.04980039224028587,
-0.04682372882962227,
-0.04684344306588173,
-0.012493642047047615,
-0.00047319201985374093,
0.08179520815610886,
-0.06445779651403427,
0.03638139367103577,
0.04403159022331238,
-0.05772855877876282,
-0.04386552795767784,
0.... | -0.003085 |
return err } if u.Scheme != "demoscheme" { return fmt.Errorf("Invalid Scheme. Want %s, Got %s", "demoscheme", u.Scheme) } if u.Path == "" { return errors.New("Empty path.") } return nil } ``` You'll also need to add the `net/url` as `neturl` and `"errors"` package to your list of imports at the top of the file. ``` {{%... | https://github.com/tektoncd/pipeline/blob/main//docs/how-to-write-a-resolver.md | main | tekton | [
-0.0046675242483615875,
0.0035525436978787184,
-0.090790294110775,
-0.018129723146557808,
-0.03484465554356575,
-0.04917525127530098,
0.05871421471238136,
0.12755687534809113,
-0.09906596690416336,
-0.008546420373022556,
-0.05578944459557533,
-0.08653932064771652,
0.00683470256626606,
0.09... | 0.029343 |
to resolve the requested file or resource. func (r \*resolver) Resolve(ctx context.Context, req \*v1beta1.ResolutionRequestSpec) (framework.ResolvedResource, error) { return &myResolvedResource{}, nil } // our hard-coded resolved file to return const pipeline = ` apiVersion: tekton.dev/v1beta1 kind: Pipeline metadata: ... | https://github.com/tektoncd/pipeline/blob/main//docs/how-to-write-a-resolver.md | main | tekton | [
-0.09401368349790573,
0.058261532336473465,
0.003383415751159191,
0.022077400237321854,
-0.036928799003362656,
-0.06836098432540894,
0.00534867262467742,
0.07438091933727264,
-0.03136816248297691,
0.001394264167174697,
-0.10225461423397064,
-0.07384304702281952,
-0.06803660094738007,
0.052... | 0.065343 |
let's submit a request for its hard-coded pipeline. Create a file called `test-request.yaml` with the following content: ```yaml apiVersion: resolution.tekton.dev/v1beta1 kind: ResolutionRequest metadata: name: test-request labels: resolution.tekton.dev/type: demo ``` And submit this request with the following command:... | https://github.com/tektoncd/pipeline/blob/main//docs/how-to-write-a-resolver.md | main | tekton | [
0.030507799237966537,
-0.0028248364105820656,
-0.023667525500059128,
-0.03216571360826492,
-0.04415177181363106,
-0.08022820204496384,
-0.06995990127325058,
0.024011824280023575,
0.07266751676797867,
0.07979044318199158,
-0.04646196961402893,
-0.09357839822769165,
-0.047084417194128036,
-0... | 0.08524 |
# Migrating from v1alpha1.Run to v1beta1.CustomRun This document describes how to migrate from `v1alpha1.Run` and `v1beta1.CustomRun` - [Changes to fields](#changes-to-fields) - [Changes to the specification](#changes-to-the-specification) - [Changes to the reference](#changes-to-the-reference) - [Support `PodTemplate`... | https://github.com/tektoncd/pipeline/blob/main//docs/migrating-v1alpha1.Run-to-v1beta1.CustomRun.md | main | tekton | [
0.022341620177030563,
-0.009705450385808945,
0.007476653438061476,
-0.02392195537686348,
0.04156586900353432,
0.014636601321399212,
-0.08092345297336578,
0.017532410100102425,
-0.05376708507537842,
0.02008165419101715,
-0.018409382551908493,
-0.005529511254280806,
-0.09046480059623718,
-0.... | 0.0835 |
Succeeded Status: Unknown Reason: Running ``` Now it failed for some reasons but has remaining retries, instead of setting Conditions as failed on TimedOut: ```yaml Status: Conditions: - Type: Succeeded Status: False Reason: Failed ``` We \*\*recommend\*\* you to do archive the failure status to `customRun.Status.retri... | https://github.com/tektoncd/pipeline/blob/main//docs/migrating-v1alpha1.Run-to-v1beta1.CustomRun.md | main | tekton | [
0.002544447546824813,
-0.04673530161380768,
-0.013813436031341553,
-0.007219589315354824,
0.013881610706448555,
-0.01052936166524887,
-0.05268425866961479,
-0.0008847306598909199,
-0.08448051661252975,
0.008016061969101429,
-0.02113652229309082,
-0.038033436983823776,
-0.0321207232773304,
... | 0.032239 |
# TaskRuns - [Overview](#overview) - [Configuring a `TaskRun`](#configuring-a-taskrun) - [Specifying the target `Task`](#specifying-the-target-task) - [Tekton Bundles](#tekton-bundles) - [Remote Tasks](#remote-tasks) - [Specifying `Parameters`](#specifying-parameters) - [Propagated Parameters](#propagated-parameters) -... | https://github.com/tektoncd/pipeline/blob/main//docs/taskruns.md | main | tekton | [
-0.039213601499795914,
0.027087651193141937,
-0.0342029444873333,
0.022113962098956108,
0.013560584746301174,
-0.002244020579382777,
0.01844276487827301,
0.020770953968167305,
-0.07024145871400833,
0.037665482610464096,
0.012216426432132721,
-0.12022880464792252,
-0.0011998825939372182,
0.... | 0.140739 |
[beta features](./additional-configs.md#beta-features). ```yaml spec: taskRef: resolver: bundles params: - name: bundle value: docker.io/myrepo/mycatalog - name: name value: echo-task - name: kind value: Task ``` You may also specify a `tag` as you would with a Docker image which will give you a repeatable reference to... | https://github.com/tektoncd/pipeline/blob/main//docs/taskruns.md | main | tekton | [
-0.03630535677075386,
0.008970254100859165,
0.017891420051455498,
0.016872603446245193,
0.03465699031949043,
0.0030810863245278597,
0.08314819633960724,
0.00639124121516943,
-0.03464671969413757,
-0.006288150791078806,
-0.04586966708302498,
-0.055328190326690674,
-0.009383371099829674,
0.0... | 0.067139 |
kind: TaskRun metadata: generateName: object-param-result- spec: params: - name: gitrepo value: commit: sha123 url: xyz.com taskSpec: steps: - name: echo-object-params image: bash args: - echo - --url=$(params.gitrepo.url) - --commit=$(params.gitrepo.commit) ``` On executing the task run, the object parameters will be ... | https://github.com/tektoncd/pipeline/blob/main//docs/taskruns.md | main | tekton | [
-0.013199830427765846,
-0.003960741683840752,
-0.05945732444524765,
0.015146719291806221,
-0.03437173366546631,
-0.07332038879394531,
-0.05747959017753601,
0.02159745618700981,
0.05048568919301033,
0.09558586031198502,
-0.009560270234942436,
-0.017925770953297615,
-0.013827180489897728,
0.... | 0.07543 |
`Workspaces`, you must map those `Workspaces` to the corresponding physical volumes in your `TaskRun` definition. For example, you can map a `PersistentVolumeClaim` volume to a `Workspace` as follows: ```yaml workspaces: - name: myworkspace # must match workspace name in the Task persistentVolumeClaim: claimName: mypvc... | https://github.com/tektoncd/pipeline/blob/main//docs/taskruns.md | main | tekton | [
-0.03774011880159378,
-0.14483019709587097,
-0.022328916937112808,
0.0009715022752061486,
-0.02285626344382763,
0.0006934042321518064,
-0.002982023172080517,
0.037430230528116226,
0.02163565531373024,
0.0044759176671504974,
-0.009777828119695187,
-0.061261944472789764,
0.053412385284900665,
... | 0.014221 |
`Sidecar` exits with an error, disregarding the exit codes of the container images that actually executed the `Steps` inside the `Pod`. Only the above command is affected. The `Pod's` description correctly denotes a "Failed" status and the container statuses correctly denote their exit codes and reasons. ### Configurin... | https://github.com/tektoncd/pipeline/blob/main//docs/taskruns.md | main | tekton | [
0.010930598713457584,
0.01963963732123375,
0.007988004013895988,
-0.008376507088541985,
0.04929712414741516,
-0.03424155339598656,
-0.04613489285111427,
0.0231891181319952,
-0.03904805704951286,
0.015245523303747177,
0.03179153427481651,
-0.05170975252985954,
-0.036528170108795166,
0.01967... | 0.080929 |
`1m`, `60s`, and `0`. If a `TaskRun` runs longer than its timeout value, the pod associated with the `TaskRun` will be deleted. This means that the logs of the `TaskRun` are not preserved. The deletion of the `TaskRun` pod is necessary in order to stop `TaskRun` step containers from running. The global default timeout ... | https://github.com/tektoncd/pipeline/blob/main//docs/taskruns.md | main | tekton | [
0.03265171870589256,
0.04584735259413719,
-0.016454866155982018,
0.005141756031662226,
0.029345223680138588,
-0.04398796707391739,
-0.0910295695066452,
-0.00709674134850502,
0.07373727113008499,
0.039139315485954285,
0.007473083678632975,
-0.007113960571587086,
-0.04145519807934761,
0.0205... | 0.092002 |
- This field is a list. The list has one entry per `sidecar` in the manifest. Each entry represents the imageid of the corresponding sidecar. - `spanContext` - Contains tracing span context fields. ## Monitoring execution status As your `TaskRun` executes, its `status` field accumulates information on the execution of ... | https://github.com/tektoncd/pipeline/blob/main//docs/taskruns.md | main | tekton | [
0.06611694395542145,
0.05967644974589348,
0.012392974458634853,
0.025062235072255135,
0.08819766342639923,
-0.01689883880317211,
0.02611074037849903,
0.0036799749359488487,
0.045334041118621826,
0.0309021957218647,
0.013593806885182858,
-0.024401100352406502,
0.006907485891133547,
-0.00560... | 0.196047 |
| `Pod` Name | |----------------------------------------------------------------------------|-----------------------------------------------------------------| | task-run | task-run-pod | | task-run-0123456789-0123456789-0123456789-0123456789-0123456789-0123456789 | task-run-0123456789-01234560d38957287bb0283c59440df14... | https://github.com/tektoncd/pipeline/blob/main//docs/taskruns.md | main | tekton | [
-0.03128030151128769,
-0.019172629341483116,
-0.04121842235326767,
-0.03736404702067375,
-0.0812576487660408,
-0.04239925369620323,
0.029149850830435753,
-0.011235509067773819,
0.03560134023427963,
0.03389217332005501,
0.014920520596206188,
-0.008540622889995575,
0.006443299353122711,
-0.0... | 0.123858 |
[Example `TaskRun` with an embedded `Task`](#example-taskrun-with-an-embedded-task) - [Example of Using custom `ServiceAccount` credentials](#example-of-using-custom-serviceaccount-credentials) - [Example of Running Step Containers as a Non Root User](#example-of-running-step-containers-as-a-non-root-user) ### Example ... | https://github.com/tektoncd/pipeline/blob/main//docs/taskruns.md | main | tekton | [
-0.06351090967655182,
-0.040837377309799194,
-0.08311444520950317,
-0.0067446609027683735,
-0.0211862251162529,
-0.07714899629354477,
0.03672266751527786,
0.01507131103426218,
0.049669936299324036,
0.038935065269470215,
-0.017784228548407555,
-0.02394072152674198,
0.05643090605735779,
0.03... | 0.10896 |
delegate the responsibility of managing a `TaskRun`'s lifecycle to an external controller. When this field is set to a value other than `"tekton.dev/pipeline"`, the Tekton Pipeline controller will ignore the `TaskRun`, allowing your external controller to take full control. This delegation enables several advanced use ... | https://github.com/tektoncd/pipeline/blob/main//docs/taskruns.md | main | tekton | [
-0.028254177421331406,
-0.025138771161437035,
-0.043458130210638046,
0.025202684104442596,
-0.027146872133016586,
-0.06690123677253723,
-0.04750176891684532,
0.029103050008416176,
0.07726152241230011,
0.06324205547571182,
-0.00994371809065342,
-0.07370854169130325,
-0.003408710937947035,
0... | 0.101331 |
# Events in Tekton Tekton's controllers emits [Kubernetes events](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#event-v1-core) when `TaskRuns` and `PipelineRuns` execute. This allows you to monitor and react to what's happening during execution by retrieving those events using the `kubectl descri... | https://github.com/tektoncd/pipeline/blob/main//docs/events.md | main | tekton | [
-0.03399219363927841,
0.032221805304288864,
0.014770525507628918,
0.003937744535505772,
0.04757169261574745,
-0.07004661113023758,
0.0024959621950984,
-0.04859571158885956,
0.164095938205719,
0.04914022237062454,
-0.022529104724526405,
-0.12171322852373123,
-0.036908622831106186,
-0.026728... | 0.158964 |
``` Other HTTP headers are: ``` "Accept-Encoding": "gzip", "Connection": "close", "Content-Length": "3519", "Content-Type": "application/json", "User-Agent": "Go-http-client/1.1" ``` The payload is JSON, a map with a single root key `taskRun` or `pipelineRun`, depending on the source of the event. Inside the root key, ... | https://github.com/tektoncd/pipeline/blob/main//docs/events.md | main | tekton | [
-0.020253222435712814,
0.10780374705791473,
-0.0712038204073906,
-0.017615284770727158,
0.004516633227467537,
-0.08357322961091995,
-0.04262180253863335,
0.0226147323846817,
0.04183829575777054,
0.008446963503956795,
-0.02369632013142109,
-0.07637173682451248,
-0.021616388112306595,
0.0489... | 0.078207 |
# Variable Substitutions Supported by `Tasks` and `Pipelines` This page documents the variable substitutions supported by `Tasks` and `Pipelines`. For instructions on using variable substitutions see the relevant section of [the Tasks doc](tasks.md#using-variable-substitution). \*\*Note:\*\* Tekton does not escape the ... | https://github.com/tektoncd/pipeline/blob/main//docs/variables.md | main | tekton | [
-0.034989237785339355,
0.057059288024902344,
0.0038734888657927513,
0.02758386917412281,
-0.08285512030124664,
-0.00933139119297266,
0.0454244539141655,
0.018301041796803474,
-0.0468863807618618,
-0.002705658320337534,
-0.058637842535972595,
-0.07775242626667023,
0.0290855560451746,
0.0457... | 0.090168 |
the `Task` | ## Variables available in a `Task` | Variable | Description | |----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| | `params.` | The value of the parameter at runtime. | | `par... | https://github.com/tektoncd/pipeline/blob/main//docs/variables.md | main | tekton | [
-0.016346588730812073,
0.04220166057348251,
-0.12858887016773224,
0.02698219195008278,
-0.09444800764322281,
-0.0061242468655109406,
0.062192924320697784,
0.07706720381975174,
-0.050760794430971146,
-0.0016050549456849694,
0.015340560115873814,
-0.021181948482990265,
0.02771342545747757,
-... | 0.10196 |
| | `Task` | `spec.sidecars[].env.valueFrom.configMapKeyRef.key` | | `Task` | `spec.sidecars[].volumeMounts.name` | | `Task` | `spec.sidecars[].volumeMounts.mountPath` | | `Task` | `spec.sidecars[].volumeMounts.subPath` | | `Task` | `spec.sidecars[].command` | | `Task` | `spec.sidecars[].args` | | `Task` | `spec.sideca... | https://github.com/tektoncd/pipeline/blob/main//docs/variables.md | main | tekton | [
0.0373469702899456,
-0.05408942699432373,
-0.09305771440267563,
0.016430918127298355,
0.018594548106193542,
0.000647872977424413,
0.05122954398393631,
0.08139290660619736,
-0.04563684016466141,
0.013600099831819534,
0.034059152007102966,
-0.07140906900167465,
0.0665234625339508,
-0.0015026... | -0.000834 |
This document describes additional options to configure your Tekton Pipelines installation. ## Table of Contents - [Configuring built-in remote Task and Pipeline resolution](#configuring-built-in-remote-task-and-pipeline-resolution) - [Configuring CloudEvents notifications](#configuring-cloudevents-notifications) - [Co... | https://github.com/tektoncd/pipeline/blob/main//docs/additional-configs.md | main | tekton | [
-0.012329024262726307,
0.018479811027646065,
-0.02888392098248005,
-0.03088143840432167,
-0.04227522388100624,
-0.01576714776456356,
-0.06791579723358154,
0.03884536400437355,
-0.05795624479651451,
0.034106332808732986,
-0.017981762066483498,
-0.07939957827329636,
-0.02774236537516117,
0.0... | 0.029885 |
args: ["echo $TEST\_TEKTON "] env: - name: "TEST\_TEKTON" value: "true" --- apiVersion: tekton.dev/v1beta1 kind: TaskRun metadata: name: mytaskrun namespace: default spec: taskRef: name: mytask podTemplate: env: - name: "TEST\_TEKTON" value: "false" ``` \_In the above example the environment variable `TEST\_TEKTON` wil... | https://github.com/tektoncd/pipeline/blob/main//docs/additional-configs.md | main | tekton | [
0.04497229680418968,
0.03879328444600105,
-0.029028289020061493,
-0.007833477109670639,
-0.020007427781820297,
-0.009579123929142952,
0.03127424046397209,
0.038048386573791504,
0.015821998938918114,
0.039056818932294846,
-0.032592158764600754,
-0.0991394892334938,
-0.08334042876958847,
0.0... | 0.093809 |
`1s` - `10ms` (for fast polling in tests) \*\*Note:\*\* The `default-sidecar-log-polling-interval` setting is only applicable when results are created using the [sidecar approach](#enabling-larger-results-using-sidecar-logs). \*\*Note:\*\* The `\_example` key in the provided [config-defaults.yaml](./../config/config-de... | https://github.com/tektoncd/pipeline/blob/main//docs/additional-configs.md | main | tekton | [
-0.0012852131621912122,
0.014300904236733913,
-0.0017766220262274146,
0.023484939709305763,
-0.0679488554596901,
-0.061126213520765305,
-0.05939875915646553,
0.0015238395426422358,
0.000390254775993526,
0.006116366945207119,
0.004360409453511238,
-0.07672771066427231,
-0.05308414250612259,
... | 0.107238 |
sidecar support. This will allow Tekton sidecars to run as Kubernetes sidecars. Must be using Kubernetes v1.29 or greater. For example: ```yaml apiVersion: v1 kind: ConfigMap metadata: name: feature-flags data: enable-api-fields: "alpha" # Allow alpha fields to be used in Tasks and Pipelines. ``` - `trusted-resources-v... | https://github.com/tektoncd/pipeline/blob/main//docs/additional-configs.md | main | tekton | [
-0.01425119861960411,
0.0547918938100338,
0.005114021711051464,
-0.008543990552425385,
0.04391989856958389,
-0.0072707864455878735,
-0.05664636194705963,
-0.0018167232628911734,
-0.04392195865511894,
0.015810765326023102,
0.018492527306079865,
-0.08713139593601227,
-0.02528233267366886,
0.... | 0.105326 |
-n tekton-pipelines -p '{"data":{"enable-api-fields":"beta"}}'`. Features currently in "beta" are: | Feature | Proposal | Alpha Release | Beta Release | Individual Flag | |:------------------------------------------------------------------------------------------------------|:-------------------------------------------... | https://github.com/tektoncd/pipeline/blob/main//docs/additional-configs.md | main | tekton | [
-0.004742298275232315,
0.07185356318950653,
-0.012931867502629757,
0.014829469844698906,
-0.0015592009294778109,
-0.030092697590589523,
-0.03550150245428085,
0.019044727087020874,
-0.03367433324456215,
-0.0270362701267004,
0.005140033084899187,
-0.08185159415006638,
-0.09232822805643082,
-... | 0.077684 |
the [feature-flags configMap](#customizing-the-pipelines-controller-behavior). This configuration option applies a [SecurityContext](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/) to any containers injected into TaskRuns by the Pipelines controller. If the [Affinity Assistants](affinityassi... | https://github.com/tektoncd/pipeline/blob/main//docs/additional-configs.md | main | tekton | [
0.01766999065876007,
0.031645748764276505,
-0.043253570795059204,
-0.025534898042678833,
0.0287442859262228,
-0.03808537498116493,
0.011865672655403614,
0.002114382106810808,
0.015300624072551727,
0.012642409652471542,
0.013502424582839012,
-0.10040856897830963,
-0.007246155291795731,
0.00... | 0.195646 |
"digest": { "sha256": "e4d77b5b8902270f37812f85feb70d57d6d0e1fed2f3b46f86baf534f19cd9c0" } }, { "name": "gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/nop", "digest": { "sha256": "59b5304bcfdd9834150a2701720cf66e3ebe6d6e4d361ae1612d9430089591f8" } }, { "name": "gcr.io/tekton-releases/github.com/tektoncd/pipel... | https://github.com/tektoncd/pipeline/blob/main//docs/additional-configs.md | main | tekton | [
-0.022261125966906548,
0.06768708676099777,
-0.06364510208368301,
-0.09678523242473602,
0.0163973867893219,
-0.13702163100242615,
0.005216178018599749,
-0.026352079585194588,
0.019433388486504555,
-0.0027205345686525106,
0.03494558483362198,
-0.10233598202466965,
-0.037178583443164825,
-0.... | 0.05458 |
pipelinerun and taskrun. The default value of disable-inline-spec is "", which means inline specification is enabled in all cases. ## Exponential Backoff for TaskRun and CustomRun Creation By default, when Tekton Pipelines attempts to create a TaskRun or CustomRun resource and encounters an error, the controller will r... | https://github.com/tektoncd/pipeline/blob/main//docs/additional-configs.md | main | tekton | [
-0.0724266842007637,
0.026565946638584137,
-0.038594845682382584,
0.08549255132675171,
0.006676723249256611,
-0.06133123114705086,
-0.08465535193681717,
-0.014501524157822132,
0.0038613108918070793,
0.028797177597880363,
0.012179135344922543,
-0.01758085936307907,
-0.020664332434535027,
-0... | 0.096176 |
Next steps To get started with Tekton check the [Introductory tutorials][quickstarts], the [how-to guides][howtos], and the [examples folder][examples]. --- {{% comment %}} Except as otherwise noted, the content of this page is licensed under the [Creative Commons Attribution 4.0 License][cca4], and code samples are li... | https://github.com/tektoncd/pipeline/blob/main//docs/additional-configs.md | main | tekton | [
-0.12323174625635147,
0.03853561356663704,
-0.09468017518520355,
-0.020999059081077576,
0.011026610620319843,
-0.07079312205314636,
-0.024659104645252228,
0.03086947649717331,
-0.02032855525612831,
0.02927420102059841,
0.04372105002403259,
-0.04626870155334473,
-0.005469282623380423,
-0.01... | 0.104124 |
# Resolver Template This directory contains a working Resolver based on the instructions from the [developer howto in the docs](../how-to-write-a-resolver.md). ## Resolver Type This Resolver responds to type `demo`. ## Parameters | Name | Desccription | Example Value | |--------|------------------------------|---------... | https://github.com/tektoncd/pipeline/blob/main//docs/resolver-template/README.md | main | tekton | [
-0.11569975316524506,
-0.025027599185705185,
-0.015562497079372406,
-0.04463398829102516,
-0.0273800827562809,
-0.08366256207227707,
-0.08043204247951508,
0.07499323040246964,
-0.014974758960306644,
0.053784631192684174,
0.004081366118043661,
0.013385182246565819,
0.003277071285992861,
0.0... | -0.006755 |
# Results Lifecycle This section gives an overview of the results lifecycle in `Tekton Pipelines`. ## Results definition and usage Tasks can define results by adding a result on the Task spec. For more information, see ["Emitting Results"](../tasks.md#emitting-results). Users are encouraged to use variable substitution... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/results-lifecycle.md | main | tekton | [
-0.03490343689918518,
0.04810232296586037,
-0.07457201927900314,
0.05465395748615265,
0.01089161541312933,
-0.037145957350730896,
-0.04081335663795471,
0.06553729623556137,
0.040061723440885544,
0.01904628612101078,
0.0087183378636837,
-0.03435870632529259,
-0.012936213985085487,
0.0208293... | 0.112827 |
## Kubernetes objects Before learning about how Tekton works, it's useful to take some time to understand what a Kubernetes object is. Please see [Understanding Kubernetes objects](https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/) for an overview of working with objects. Kubernetes ... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/controller-logic.md | main | tekton | [
-0.07380719482898712,
0.01953066885471344,
-0.00736594945192337,
-0.03177661448717117,
-0.03526837378740311,
-0.026703432202339172,
0.03499683737754822,
0.036031290888786316,
0.08324059098958969,
0.028765728697180748,
-0.011943694204092026,
-0.06803406774997711,
-0.0363171212375164,
-0.025... | 0.246053 |
a pod to run the TaskRun and exits the reconcile loop. Later, the pod completes, resulting in another event that triggers reconciliation of the TaskRun that owns it. The reconciler sees that the TaskRun has a pod associated with it, and that the pod has completed. It updates the TaskRun status to mark it as completed a... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/controller-logic.md | main | tekton | [
0.0042096939869225025,
-0.015842100605368614,
0.05865811929106712,
0.021243184804916382,
0.07309150695800781,
-0.032061103731393814,
-0.013196823187172413,
-0.05396660417318344,
0.09525804966688156,
0.009508540853857994,
-0.01120503805577755,
0.05774463713169098,
-0.061801712960004807,
-0.... | 0.194867 |
# Support for running in multi-tenant configuration Multi-tenancy for Tekton is intended as running multiple instances of the Tekton control plane in a single Kubernetes cluster, with each control plane responsible for reconciliation of the Tekton resources in a single namespace. This type of setup involves various asp... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/multi-tenant-support.md | main | tekton | [
-0.05913015455007553,
0.034213837236166,
-0.06341128051280975,
-0.01496325246989727,
-0.02938816510140896,
-0.03545723855495453,
0.008569133467972279,
-0.014803513884544373,
0.0671810656785965,
0.030602186918258667,
0.013632353395223618,
-0.1340532898902893,
0.014872872270643711,
-0.053698... | 0.13633 |
in the cluster. The conversion webhook is bundled in a single binary with the other webhooks, so today it's not possible to run multiple validation and mutation webhooks and a single conversion webhook. [TEP-0129](https://github.com/tektoncd/community/blob/main/teps/0129-multiple-tekton-instances-per-cluster.md) will c... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/multi-tenant-support.md | main | tekton | [
-0.08585168421268463,
0.034005314111709595,
-0.09103099256753922,
-0.05056575685739517,
0.05001315474510193,
-0.10138006508350372,
-0.0454280711710453,
-0.058248620480298996,
-0.001918111927807331,
-0.008219100534915924,
0.012925194576382637,
-0.1622626781463623,
0.06851723045110703,
-0.08... | 0.077254 |
# Affinity Assistant [Specifying `Workspaces` in a `Pipeline`](../workspaces.md#specifying-workspace-order-in-a-pipeline-and-affinity-assistants) explains how an affinity assistant is created when a `persistentVolumeClaim` is used as a volume source for a `workspace` in a `pipelineRun`. Please refer to the same section... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/affinity-assistant.md | main | tekton | [
-0.03639132156968117,
-0.041786711663007736,
-0.0041998629458248615,
0.05543766915798187,
0.011117812246084213,
-0.06963276863098145,
-0.01673584245145321,
-0.041093163192272186,
0.020929837599396706,
0.005595418158918619,
-0.018110185861587524,
0.01571773737668991,
-0.015263146720826626,
... | 0.178237 |
# API Versioning ## Adding a new API version to a Pipelines CRD 1. Read the [Kubernetes documentation](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/) on versioning CRDs, especially the section on [specifying multiple versions](https://kubernetes.io/docs/tasks... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/api-versioning.md | main | tekton | [
-0.027585292235016823,
-0.002599122002720833,
0.044239409267902374,
-0.08877050131559372,
-0.03521209955215454,
0.0024608492385596037,
-0.08179610967636108,
0.000043017811549361795,
0.04377482086420059,
0.0019808977376669645,
0.009368961676955223,
-0.05257605016231537,
-0.05386501923203468,
... | -0.010585 |
# Resources labelling Tekton applications sometimes need to find resources belonging to other applications (dashboard needs to talk to pipelines and triggers, triggers needs to talk to pipelines, etc.). In order to facilitate identifying resources that belong to an application, the following [recommended labels](https:... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/resources-labelling.md | main | tekton | [
-0.01911630854010582,
0.04859522357583046,
-0.07497163861989975,
-0.026747165247797966,
0.053205255419015884,
0.005506716202944517,
0.10292831063270569,
0.031336404383182526,
0.13500003516674042,
-0.044402360916137695,
-0.014900203794240952,
-0.12084408104419708,
0.02126356028020382,
0.000... | 0.177875 |
# Developer docs This document is aimed at helping maintainers/developers of project understand the complexity. We also recommend checking out the [Teknical Tekton](https://www.youtube.com/channel/UCUEuKDqyRnGFCE7FpainSpQ) channel for training and tutorials on Tekton! ## Contents - Developing on Tekton: - [Local Setup]... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/README.md | main | tekton | [
-0.027500338852405548,
0.007596541196107864,
-0.027167486026883125,
-0.036308154463768005,
0.018182028084993362,
-0.09189491719007492,
-0.009019939228892326,
0.028415927663445473,
0.019221248105168343,
0.06166347861289978,
-0.009163342416286469,
-0.09863346070051193,
-0.03495064750313759,
... | 0.202399 |
# API Changes ✋ Before reading this, please read the [API Compatibility Policy](../../api\_compatibility\_policy.md) ## CustomRuns Before adding an optional field to the spec or status of `CustomRun`, consider whether it could be part of the custom spec or custom status instead. New fields should be added to the spec o... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/api-changes.md | main | tekton | [
-0.009347634389996529,
0.01423587091267109,
0.0010175067000091076,
0.05260724946856499,
0.0294039286673069,
0.01904338039457798,
-0.11462155729532242,
0.07315947115421295,
-0.05712078511714935,
0.03510425239801407,
0.07113675028085709,
0.049030717462301254,
-0.05366184189915657,
0.01429318... | 0.022401 |
compatibility of Go libraries when possible. [Keeping Your Modules Compatible](https://go.dev/blog/module-compatibility) offers some helpful suggestions. | https://github.com/tektoncd/pipeline/blob/main//docs/developers/api-changes.md | main | tekton | [
-0.021037081256508827,
-0.03993367403745651,
-0.06600510329008102,
-0.06901586055755615,
-0.005926196463406086,
0.03147710859775543,
-0.0874810740351677,
0.029327305033802986,
-0.09462951868772507,
-0.07411458343267441,
0.08807709813117981,
0.08303839713335037,
-0.07373224943876266,
0.1263... | -0.033087 |
# Tracing setup This sections shows how to enable tracing for tekton reconcilers and capture traces in Jaeger ## Prerequisites Jaeger should be installed and accessible from the cluster. The easiest way to set it up is using helm as below the following command installs Jaeger in `jaeger` namespace ``` helm repo add jae... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/tracing.md | main | tekton | [
-0.07812473922967911,
0.0013394105480983853,
0.01505457516759634,
-0.031756605952978134,
-0.011503854766488075,
-0.022128568962216377,
-0.022492986172437668,
-0.015327793546020985,
0.009043030440807343,
0.02392095886170864,
0.003917585127055645,
-0.08815260231494904,
0.01762419566512108,
-... | 0.084557 |
## Introduction FIPS compliance requires compiling the project with a Go FIPS-compliant compiler (e.g., golang-fips) and using dynamic linking. This approach works for most binaries in tektoncd/pipeline, except for the entrypoint, which must be statically compiled to ensure it runs in any environment, regardless of lib... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/fips.md | main | tekton | [
-0.04234270006418228,
0.0998336523771286,
-0.024434737861156464,
-0.035327404737472534,
-0.021978216245770454,
-0.04575522989034653,
-0.04782916605472565,
0.0603598952293396,
-0.04851550608873367,
-0.012901532463729382,
-0.01391314622014761,
-0.04456179216504097,
-0.0671071782708168,
0.089... | 0.061557 |
# Local Setup This section provides guidelines for running Tekton on your local workstation via the following methods: - [Docker for Desktop](#using-docker-desktop) - [Minikube](#using-minikube) ## Using Docker Desktop ### Prerequisites Complete these prerequisites to run Tekton locally using Docker Desktop: - Install ... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/local-setup.md | main | tekton | [
-0.0014288886450231075,
0.07657454162836075,
-0.03917798772454262,
-0.04672077298164368,
-0.018285389989614487,
-0.049151670187711716,
-0.060780689120292664,
0.09586995095014572,
-0.04602309688925743,
0.04213406890630722,
-0.03964345157146454,
-0.09431617707014084,
0.0015598854515701532,
0... | 0.001251 |
# Feature Versioning The stability levels of features (feature versioning) are independent of CRD [API versioning](./api-versioning.md). You may follow the existing Tekton feature flags demo for detailed reference: - [Tekton Per-feature Flag Demo Slides](https://docs.google.com/presentation/d/1MAwBTKYUN40SZcd6om6LMw217... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/feature-versioning.md | main | tekton | [
-0.055740002542734146,
0.02390764094889164,
0.01083730161190033,
-0.02003663405776024,
0.05227255821228027,
-0.038751665502786636,
-0.059119001030921936,
0.005153348669409752,
-0.08072361350059509,
-0.02290286123752594,
-0.01794920675456524,
-0.056956350803375244,
-0.018915260210633278,
-0... | 0.001193 |
new function signatures. ### Guarding Validations with Feature Gates Just because your application code might be correctly observing the feature gate flag doesn't mean you're done yet! When a user submits a Tekton resource it's validated by Pipelines' webhook. Here too you'll need to ensure your new features aren't acc... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/feature-versioning.md | main | tekton | [
-0.041098978370428085,
0.054991792887449265,
-0.03735164925456047,
-0.019818447530269623,
0.03214877098798752,
-0.09733607620000839,
-0.013386824168264866,
0.029736336320638657,
-0.06645793467760086,
-0.02960354834794998,
0.004073085263371468,
-0.12236745655536652,
-0.0008648824295960367,
... | 0.041734 |
This doc describes how TaskRuns are implemented using pods. ## Entrypoint rewriting and step ordering Tekton releases include a binary called the "entrypoint", which wraps the user-provided binary for each `Step` container to manage the execution order of the containers. The `entrypoint` binary has the following argume... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/taskruns.md | main | tekton | [
0.01529613882303238,
0.02481965720653534,
0.03862811252474785,
0.011456871405243874,
-0.01781907118856907,
-0.013760791160166264,
-0.025897594168782234,
0.056981250643730164,
0.07363803684711456,
0.0801178440451622,
-0.022447315976023674,
-0.0061670285649597645,
-0.003951149992644787,
0.00... | 0.185016 |
| |-- ..data -> ..2021\_09\_16\_18\_31\_06.270542700 | `-- ready -> ..data/ready |-- home |-- results |-- run `-- 0 `-- out `-- status `-- exitCode |-- scripts | |-- script-0-t4jd8 | `-- script-1-4pjwp |-- steps | |-- 0 -> /tekton/run/0/status | |-- 1 -> /tekton/run/1/status | |-- step-foo -> /tekton/run/1/status | `--... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/taskruns.md | main | tekton | [
-0.014722025021910667,
0.06162262335419655,
-0.03925267234444618,
-0.007717043161392212,
-0.0010747932828962803,
-0.04292219504714012,
-0.008228260092437267,
0.037415750324726105,
-0.012909673154354095,
0.013151849620044231,
0.05858335271477699,
-0.06369771808385849,
-0.0049515082500875,
-... | 0.070555 |
first container is actively running so none of the output files are populated yet. The `/tekton/steps` directories are symlinked to locations that do not yet exist, but will be populated during execution. ``` /tekton |-- run | |-- 0 | `-- 1 |-- steps |-- 0 -> /tekton/run/0/status |-- 1 -> /tekton/run/1/status |-- step-... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/taskruns.md | main | tekton | [
-0.05488692596554756,
0.043362390249967575,
-0.06600729376077652,
0.016999809071421623,
0.058199118822813034,
-0.07951012253761292,
-0.025400733575224876,
0.0327867791056633,
0.04242967814207077,
0.0025811109226197004,
0.07919465005397797,
-0.043676815927028656,
-0.029498087242245674,
-0.0... | 0.059817 |
`nop` has been swapped into the sidecar container's image field. See [the issue tracking this bug](https://github.com/tektoncd/pipeline/issues/1347) for the issue tracking this bug. Until this issue is resolved the best way to avoid it is to avoid overriding the `nop` image when deploying the tekton controller, or ensu... | https://github.com/tektoncd/pipeline/blob/main//docs/developers/taskruns.md | main | tekton | [
0.02260245382785797,
0.07493911683559418,
0.05878767371177673,
-0.01909659430384636,
0.04029589891433716,
-0.05692308768630028,
-0.04077626019716263,
-0.006632886361330748,
0.0652017742395401,
0.024955596774816513,
0.05390384793281555,
-0.09171165525913239,
0.0002192095562350005,
0.0085821... | 0.093686 |
# Migration Guide: v1 to v2 This guide covers the breaking changes introduced in v2 of the MCP Python SDK and how to update your code. ## Overview Version 2 of the MCP Python SDK introduces several breaking changes to improve the API, align with the MCP specification, and provide better type safety. ## Breaking Changes... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/migration.md | main | model-context-protocol-mcp | [
-0.08338426053524017,
0.02736485004425049,
0.06458518654108047,
0.00036823601112701,
0.0527360625565052,
-0.05015696585178375,
-0.06596814841032028,
0.019240306690335274,
-0.06519347429275513,
-0.0436091348528862,
-0.01430757436901331,
0.03204069659113884,
0.009028670378029346,
0.018652619... | -0.01397 |
The `McpError` exception class has been renamed to `MCPError` for consistent naming with the MCP acronym style used throughout the SDK. \*\*Before (v1):\*\* ```python from mcp.shared.exceptions import McpError try: result = await session.call\_tool("my\_tool") except McpError as e: print(f"Error: {e.error.message}") ``... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/migration.md | main | model-context-protocol-mcp | [
-0.06531819701194763,
0.009843578562140465,
0.02123439684510231,
0.06108153983950615,
-0.00983988307416439,
-0.04488489776849747,
0.001530487323179841,
0.02033623494207859,
0.03650308772921562,
-0.013726452365517616,
0.03645676374435425,
-0.017463192343711853,
0.08403428643941879,
0.005755... | 0.069945 |
the actual type ``` \*\*Available adapters:\*\* | Union Type | Adapter | |------------|---------| | `ClientRequest` | `client\_request\_adapter` | | `ServerRequest` | `server\_request\_adapter` | | `ClientNotification` | `client\_notification\_adapter` | | `ServerNotification` | `server\_notification\_adapter` | | `Cli... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/migration.md | main | model-context-protocol-mcp | [
-0.05934489145874977,
-0.005373060703277588,
-0.0034018687438219786,
0.014509356580674648,
-0.007560881786048412,
-0.06566978245973587,
-0.006579443346709013,
0.030599320307374,
-0.025766262784600258,
-0.008103934116661549,
0.03615289553999901,
-0.04773186519742012,
0.043677378445863724,
0... | 0.086879 |
client.read\_resource(str(my\_any\_url)) ``` ## Deprecations ## Bug Fixes ### Extra fields no longer allowed on top-level MCP types MCP protocol types no longer accept arbitrary extra fields at the top level. This matches the MCP specification which only allows extra fields within `\_meta` objects, not on the types the... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/migration.md | main | model-context-protocol-mcp | [
-0.06847549229860306,
0.011634204536676407,
0.03048676811158657,
0.015932176262140274,
-0.05679338425397873,
-0.09816412627696991,
-0.00019319209968671203,
0.056247174739837646,
-0.03520789369940758,
-0.019470339640975,
-0.05259605497121811,
-0.02813068963587284,
0.02344612032175064,
0.027... | -0.014261 |
# Testing MCP Servers The Python SDK provides a `Client` class for testing MCP servers with an in-memory transport. This makes it easy to write tests without network overhead. ## Basic Usage Let's assume you have a simple server with a single tool: ```python title="server.py" from mcp.server import MCPServer app = MCPS... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/testing.md | main | model-context-protocol-mcp | [
-0.02841028943657875,
0.013305401429533958,
-0.001162431901320815,
0.030425282195210457,
-0.07515258342027664,
-0.09438630938529968,
-0.049812693148851395,
0.07499580830335617,
0.00020896103524137288,
0.022886408492922783,
0.007643257267773151,
-0.0016863606870174408,
0.07668352872133255,
... | 0.022737 |
# MCP Python SDK The \*\*Model Context Protocol (MCP)\*\* allows applications to provide context for LLMs in a standardized way, separating the concerns of providing context from the actual LLM interaction. This Python SDK implements the full MCP specification, making it easy to: - \*\*Build MCP servers\*\* that expose... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/index.md | main | model-context-protocol-mcp | [
-0.04669640585780144,
-0.03348361328244209,
-0.019103651866316795,
-0.023615768179297447,
-0.01477032620459795,
-0.08355564624071121,
-0.005966216791421175,
0.04946822300553322,
0.01599201001226902,
-0.025045478716492653,
-0.03858620673418045,
-0.014843625947833061,
0.10580030828714371,
-0... | 0.129642 |
# Installation The Python SDK is available on PyPI as [`mcp`](https://pypi.org/project/mcp/) so installation is as simple as: === "pip" ```bash pip install mcp ``` === "uv" ```bash uv add mcp ``` The following dependencies are automatically installed: - [`httpx`](https://pypi.org/project/httpx/): HTTP client to handle ... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/installation.md | main | model-context-protocol-mcp | [
-0.07323024421930313,
0.007375112269073725,
-0.01437243353575468,
-0.0067839245311915874,
-0.042513757944107056,
-0.0381062813103199,
-0.03490260988473892,
0.07189161330461502,
-0.044219329953193665,
-0.06574570387601852,
-0.02270079031586647,
-0.04571429267525673,
0.027498120442032814,
0.... | 0.02363 |
# Tasks !!! warning "Experimental" Tasks are an experimental feature tracking the draft MCP specification. The API may change without notice. Tasks enable asynchronous request handling in MCP. Instead of blocking until an operation completes, the receiver creates a task, returns immediately, and the requestor polls for... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/experimental/tasks.md | main | model-context-protocol-mcp | [
-0.11120966076850891,
-0.0018751501338556409,
0.04970965534448624,
0.049458809196949005,
0.04856457561254501,
-0.13251961767673492,
-0.04497428983449936,
-0.07375340908765793,
0.01244692038744688,
0.031135104596614838,
-0.02479497529566288,
-0.016255058348178864,
0.02757520228624344,
-0.02... | 0.133608 |
result final = await session.experimental.get\_task\_result(task\_id, CallToolResult) ``` ## Next Steps - [Server Implementation](tasks-server.md) - Build task-supporting servers - [Client Usage](tasks-client.md) - Call and poll tasks from clients | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/experimental/tasks.md | main | model-context-protocol-mcp | [
-0.040677864104509354,
0.06128016486763954,
-0.03523007035255432,
0.04218868166208267,
-0.07509179413318634,
-0.04532448202371597,
0.02167457342147827,
0.013449534773826599,
0.012204432860016823,
0.06590622663497925,
-0.07543078064918518,
-0.03377341479063034,
-0.011587468907237053,
0.0289... | 0.055473 |
# Experimental Features !!! warning "Experimental APIs" The features in this section are experimental and may change without notice. They track the evolving MCP specification and are not yet stable. This section documents experimental features in the MCP Python SDK. These features implement draft specifications that ar... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/experimental/index.md | main | model-context-protocol-mcp | [
-0.1120196282863617,
-0.007029633037745953,
0.05359527841210365,
0.0752018392086029,
0.045213356614112854,
-0.11806157976388931,
-0.05684318020939827,
-0.03655082732439041,
-0.06298132240772247,
0.023716604337096214,
-0.0472770631313324,
-0.01598464697599411,
0.01985384337604046,
-0.041882... | 0.15775 |
# Server Task Implementation !!! warning "Experimental" Tasks are an experimental feature. The API may change without notice. This guide covers implementing task support in MCP servers, from basic setup to advanced patterns like elicitation and sampling within tasks. ## Quick Start The simplest way to add task support:... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/experimental/tasks-server.md | main | model-context-protocol-mcp | [
-0.08301077783107758,
-0.07835233211517334,
0.019559472799301147,
0.06928502768278122,
-0.05314663425087929,
-0.10782330483198166,
0.008899392560124397,
-0.00891122967004776,
-0.050020527094602585,
0.045271843671798706,
-0.05355600267648697,
-0.015866437926888466,
0.05909593775868416,
0.01... | 0.081472 |
await task.update\_status("Waiting for OAuth...") result = await task.elicit\_url( message="Please authorize with GitHub", url="https://github.com/login/oauth/authorize?client\_id=...", elicitation\_id="oauth-github-123", ) if result.action == "accept": # User completed OAuth flow return CallToolResult(content=[TextCon... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/experimental/tasks-server.md | main | model-context-protocol-mcp | [
-0.03011399134993553,
0.004814724903553724,
-0.021610582247376442,
0.04753273352980614,
0.01744822971522808,
-0.10345276445150375,
0.0274883434176445,
0.010745195671916008,
0.08483671396970749,
-0.01514323242008686,
-0.017360923811793327,
-0.003298875642940402,
0.049726564437150955,
-0.005... | 0.02169 |
Marks the task as `failed` 2. Sets `statusMessage` to the exception message 3. Propagates the exception (which is caught by the task group) For custom error messages, call `task.fail()` before raising. ## HTTP Transport Example For web applications, use the Streamable HTTP transport: ```python from collections.abc impo... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/experimental/tasks-server.md | main | model-context-protocol-mcp | [
-0.030887208878993988,
-0.03364057466387749,
0.013650426641106606,
0.06846883147954941,
-0.028124630451202393,
-0.07069198042154312,
0.010761592537164688,
0.026937462389469147,
-0.032830968499183655,
0.02493942156434059,
-0.01491986121982336,
-0.061570458114147186,
0.07884407043457031,
0.0... | 0.07175 |
# Client Task Usage !!! warning "Experimental" Tasks are an experimental feature. The API may change without notice. This guide covers calling task-augmented tools from clients, handling the `input\_required` status, and advanced patterns like receiving task requests from servers. ## Quick Start Call a tool as a task a... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/experimental/tasks-client.md | main | model-context-protocol-mcp | [
-0.051432304084300995,
0.015994276851415634,
0.00589585630223155,
0.11833547800779343,
-0.05010029301047325,
-0.09335649013519287,
0.029370304197072983,
0.0045078410767018795,
-0.02264432981610298,
0.0251311007887125,
-0.02936001494526863,
-0.025660820305347443,
0.016109202057123184,
-0.00... | 0.099139 |
check for and handle cancellation. ## Listing Tasks View all tasks on the server: ```python result = await session.experimental.list\_tasks() for task in result.tasks: print(f"{task.taskId}: {task.status}") # Handle pagination while result.nextCursor: result = await session.experimental.list\_tasks(cursor=result.nextCu... | https://github.com/modelcontextprotocol/python-sdk/blob/main//docs/experimental/tasks-client.md | main | model-context-protocol-mcp | [
-0.0697440430521965,
0.010921228677034378,
0.005095063243061304,
0.05926467478275299,
-0.04401524364948273,
-0.08561666309833527,
0.012623360380530357,
-0.046193186193704605,
-0.01364972349256277,
0.07182136923074722,
-0.06090893596410751,
0.022768419235944748,
0.037652160972356796,
0.0107... | 0.096111 |
\*\*[v3.0.0b1: This Beta Work](https://github.com/jlowin/fastmcp/releases/tag/v3.0.0b1)\*\* FastMCP 3.0 rebuilds the framework around three primitives: components, providers, and transforms. Providers source components dynamically—from decorators, filesystems, OpenAPI specs, remote servers, or anywhere else. Transforms... | https://github.com/jlowin/fastmcp/blob/main//docs/changelog.mdx | main | model-context-protocol-fastmcp | [
-0.13108378648757935,
0.00042836961802095175,
-0.0005770586431026459,
-0.008479312993586063,
0.06547782570123672,
-0.038778871297836304,
0.0029584772419184446,
-0.0015891920775175095,
-0.037238527089357376,
-0.038751546293497086,
0.08444209396839142,
0.021437309682369232,
-0.0033604919444769... | 0.169344 |
type: ignore[attr-defined] with isinstance assertions in tests by [@jlowin](https://github.com/jlowin) in [#2665](https://github.com/jlowin/fastmcp/pull/2665) \* Add poll\_interval to TaskConfig by [@jlowin](https://github.com/jlowin) in [#2666](https://github.com/jlowin/fastmcp/pull/2666) \* Refactor task module: rena... | https://github.com/jlowin/fastmcp/blob/main//docs/changelog.mdx | main | model-context-protocol-fastmcp | [
-0.15127059817314148,
0.04572688043117523,
0.021484144032001495,
0.03935902938246727,
0.004276763182133436,
-0.04014455899596214,
-0.010344954207539558,
-0.023304225876927376,
-0.06927920877933502,
-0.04794713482260704,
0.009229335933923721,
-0.00139099289663136,
0.0459330715239048,
0.0508... | 0.03886 |
up type ignores by [@jlowin](https://github.com/jlowin) in [#2859](https://github.com/jlowin/fastmcp/pull/2859) \* Run sync tools/resources/prompts in threadpool automatically by [@jlowin](https://github.com/jlowin) in [#2865](https://github.com/jlowin/fastmcp/pull/2865) \* Add timeout parameter for tool foreground exe... | https://github.com/jlowin/fastmcp/blob/main//docs/changelog.mdx | main | model-context-protocol-fastmcp | [
-0.10464019328355789,
0.008319885469973087,
-0.0007149392040446401,
0.0022260055411607027,
0.05220969021320343,
-0.06029954552650452,
-0.024180101230740547,
-0.005247987806797028,
-0.01592825911939144,
-0.0487261526286602,
0.007979772984981537,
0.0004075748147442937,
0.03533107414841652,
-... | 0.056019 |
client hanging on HTTP 4xx/5xx errors by [@jlowin](https://github.com/jlowin) in [#2803](https://github.com/jlowin/fastmcp/pull/2803) \* Fix unawaited coroutine warning and treat as test error by [@jlowin](https://github.com/jlowin) in [#2806](https://github.com/jlowin/fastmcp/pull/2806) \* Fix keep\_alive passthrough ... | https://github.com/jlowin/fastmcp/blob/main//docs/changelog.mdx | main | model-context-protocol-fastmcp | [
-0.07078798860311508,
0.01820201613008976,
-0.03697439655661583,
-0.03418738767504692,
0.021485069766640663,
-0.04085877910256386,
-0.05985947325825691,
0.02974093146622181,
-0.06219720095396042,
-0.03170866146683693,
0.07023856788873672,
-0.02134827896952629,
-0.032927755266427994,
-0.036... | 0.024118 |
where cancelled tasks accumulated instead of being cleaned up. Bumps pydocket to ≥0.17.2. ## What's Changed ### Enhancements 🔧 \* Bump pydocket to 0.17.2 (memory leak fix) by [@chrisguidry](https://github.com/chrisguidry) in [#2992](https://github.com/jlowin/fastmcp/pull/2992) \*\*Full Changelog\*\*: [v2.14.4...v2.14.... | https://github.com/jlowin/fastmcp/blob/main//docs/changelog.mdx | main | model-context-protocol-fastmcp | [
-0.1306883543729782,
0.026606282219290733,
0.044043105095624924,
-0.0017367522232234478,
0.095933698117733,
-0.036664530634880066,
-0.04923522472381592,
-0.004197295755147934,
-0.04613124579191208,
0.0003815348900388926,
0.11977070569992065,
0.03307768702507019,
-0.0370151549577713,
0.0271... | -0.036992 |
with tools (SEP-1577), enabling servers to pass tools to `ctx.sample()` for agentic workflows where the LLM can automatically execute tool calls in a loop. The new `ctx.sample\_step()` method provides single LLM calls that return `SampleStep` objects for custom control flow, while `result\_type` enables structured outp... | https://github.com/jlowin/fastmcp/blob/main//docs/changelog.mdx | main | model-context-protocol-fastmcp | [
-0.09124021232128143,
-0.04175729677081108,
-0.04154590889811516,
0.0065355077385902405,
0.03460581600666046,
-0.10175809264183044,
-0.018357813358306885,
0.010361227206885815,
0.0089931171387434,
-0.002623654203489423,
-0.035993196070194244,
-0.058868955820798874,
-0.0065900119952857494,
... | 0.155635 |
[#2570](https://github.com/jlowin/fastmcp/pull/2570) \* Correct OAuth error codes by [@jlowin](https://github.com/jlowin) in [#2578](https://github.com/jlowin/fastmcp/pull/2578) \* Prevent function signature modification by [@jlowin](https://github.com/jlowin) in [#2590](https://github.com/jlowin/fastmcp/pull/2590) \* ... | https://github.com/jlowin/fastmcp/blob/main//docs/changelog.mdx | main | model-context-protocol-fastmcp | [
-0.13465607166290283,
0.047940757125616074,
0.047478675842285156,
-0.055202651768922806,
0.013253807090222836,
-0.05385593697428703,
-0.04208476096391678,
-0.010282488539814949,
-0.049335774034261703,
-0.038999300450086594,
0.024453317746520042,
0.0384020172059536,
0.039446115493774414,
-0... | -0.014505 |
via base\_authority parameter by [@jlowin](https://github.com/jlowin) in [#2385](https://github.com/jlowin/fastmcp/pull/2385) \* Add Supabase authentication algorithm configuration by [@jlowin](https://github.com/jlowin) in [#2392](https://github.com/jlowin/fastmcp/pull/2392) ### Fixes 🐞 \* Security: Update authlib fo... | https://github.com/jlowin/fastmcp/blob/main//docs/changelog.mdx | main | model-context-protocol-fastmcp | [
-0.15112070739269257,
-0.013878883793950081,
-0.019882116466760635,
-0.05185135453939438,
0.03344913199543953,
0.03641853854060173,
-0.053365517407655716,
0.02535630762577057,
-0.06663727760314941,
-0.0012517205905169249,
0.0391572043299675,
-0.01846795529127121,
0.06496550142765045,
-0.00... | -0.038583 |
the MCP SDK version below 1.17, which introduced a change affecting FastMCP users with auth providers mounted as part of a larger application. This ensures the `.well-known` payload appears in the expected location when using FastMCP authentication providers with composite applications. ## What's Changed ### Fixes 🐞 \... | https://github.com/jlowin/fastmcp/blob/main//docs/changelog.mdx | main | model-context-protocol-fastmcp | [
-0.08118092268705368,
0.022403959184885025,
0.07590778172016144,
-0.022309336811304092,
0.07300393283367157,
-0.06809573620557785,
0.0009416945395059884,
-0.04304100573062897,
0.03699731454253197,
-0.013357606716454029,
0.09736856818199158,
0.011493383906781673,
0.025400761514902115,
-0.00... | -0.021195 |
[@zzstoatzz](https://github.com/zzstoatzz) in [#1928](https://github.com/jlowin/fastmcp/pull/1928) ### Docs 📚 \* docs: make Gemini CLI integration discoverable by [@jackwotherspoon](https://github.com/jackwotherspoon) in [#1827](https://github.com/jlowin/fastmcp/pull/1827) \* docs: update NEW tags for AI assistant int... | https://github.com/jlowin/fastmcp/blob/main//docs/changelog.mdx | main | model-context-protocol-fastmcp | [
-0.1838092803955078,
-0.020756738260388374,
0.0034036508295685053,
-0.02835622802376747,
0.023636633530259132,
-0.039857570081949234,
-0.02200729213654995,
0.01982230134308338,
-0.11483310908079147,
-0.030675267800688744,
0.03259177878499031,
0.00832295324653387,
-0.0024440865963697433,
-0... | 0.170681 |
recognized as a valid option in `fastmcp.json` configuration files, despite being supported by the CLI. This resulted in a parsing error when the CLI arguments were merged against the configuration spec. ## What's Changed ### Fixes 🐞 \* Fix streamable-http transport validation in fastmcp.json config by [@jlowin](https... | https://github.com/jlowin/fastmcp/blob/main//docs/changelog.mdx | main | model-context-protocol-fastmcp | [
-0.08999595791101456,
0.049351125955581665,
0.004692038521170616,
-0.08424516767263412,
0.0817749872803688,
-0.05357377231121063,
-0.016406970098614693,
-0.015389172360301018,
-0.013054081238806248,
-0.05846850201487541,
0.08770851045846939,
-0.007434346713125706,
-0.01490635983645916,
0.0... | -0.014165 |
authors define fallback handlers that generate sampling completions server-side when clients don't support the feature, encouraging adoption while maintaining compatibility. This release took longer than usual to ship, and for good reason: the community's aggressive testing and feedback on the authentication system hel... | https://github.com/jlowin/fastmcp/blob/main//docs/changelog.mdx | main | model-context-protocol-fastmcp | [
-0.17255215346813202,
0.03895212709903717,
0.03996550664305687,
0.007028193213045597,
0.0416361540555954,
-0.023861654102802277,
-0.028143372386693954,
-0.02299114316701889,
-0.0217414703220129,
-0.04329395666718483,
0.038794875144958496,
0.07301201671361923,
0.03345160931348801,
0.0123932... | -0.004157 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.