Overview - Zitadel/zitadel

zitadel/zitadel

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
main
96f9bbc0 docs: structure update (#11275) ### **Restructure Docs Navigation & Consolidate Core Concepts** **Summary** This PR refactors the documentation navigation to follow a clearer **User Journey** and consolidates fragmented pages to reduce redundancy. **Key Changes** * **Sidebar:** * Replaced the legacy resource-based structure with user-journey-focused categories. **Proposed Structure:** ``` Get Started ├─ Overview │ └─ Guides Overview (Brief intro to docs, persona-aligned: "Get auth working in minutes for your B2B app.") ├─ Quickstart Guide │ └─ Quickstart (Step-by-step: Sign up, spin up instance, connect app, log in – mirrors brand's 4-step guide.) ├─ Authenticate Users │ ├─ Login with ZITADEL (OIDC) │ ├─ Get ID / Access Token │ └─ Logout ├─ Examples & SDKs │ ├─ SPA / Frontend │ ├─ Web Applications │ ├─ APIs / Backend Services │ ├─ Hybrid / Full-Stack │ └─ Sample Applications (Include community-contributed examples for openness.) ├─ Key Concepts │ ├─ Instances, Orgs, Projects, Apps │ ├─ Policies (Intro) │ └─ Users & Roles └─ Use Cases ├─ B2B Integration (Tailored to multi-tenant enterprise needs.) ├─ B2C Login ├─ Multi-Tenant / SaaS ├─ Branded Login & White-Label └─ Machine-to-Machine (M2M) Configure Identity & Policies ├─ Identity Providers │ ├─ External IDPs (e.g., Google, Azure) │ └─ Custom Providers ├─ Policies │ ├─ Password Policies │ ├─ Lockout Policies │ └─ Privacy Policies ├─ Roles & Permissions │ ├─ RBAC Setup │ └─ Custom Roles └─ Compliance & Security ├─ Audits & Logs └─ Certifications (Highlight trust through openness.) Integrate & Authenticate ├─ OIDC & OAuth Flows ├─ API Access │ ├─ gRPC APIs │ └─ REST APIs ├─ SDKs │ ├─ Go │ ├─ JavaScript/TypeScript │ ├─ Python │ └─ Others (Link to community SDKs.) └─ External Integrations ├─ SAML ├─ LDAP └─ Webhooks Test & Debug ├─ Testing Tools │ ├─ Console Testing │ └─ API Playground ├─ Common Issues │ ├─ Token Errors │ └─ Integration Failures └─ Debugging Guides ├─ Logs & Monitoring └─ Error Codes Reference Deploy & Operate ├─ Deployment Options │ ├─ Cloud (ZITADEL Cloud) │ ├─ Self-Hosted (Linux, MacOS) │ ├─ Docker Compose │ └─ Kubernetes ├─ Configuration │ ├─ Environment Variables │ └─ Advanced Settings ├─ Scaling & Performance │ ├─ High Availability │ └─ Backup & Restore └─ Monitoring & Maintenance ├─ Metrics └─ Upgrades Architecture & Concepts ├─ System Architecture │ ├─ Core Components │ └─ Data Flow Diagrams (Expressive visuals per brand.) ├─ Principles │ ├─ Multi-Tenancy │ └─ Open Standards (OIDC, SAML) └─ Advanced Topics ├─ Customization └─ Extensibility (Open-source contributions.) Product, Releases & Support ├─ Product Features │ ├─ Roadmap (Public, for transparency.) │ └─ Pricing & Tiers ├─ Releases │ ├─ Changelog │ └─ Upgrade Guides └─ Support Resources ├─ Community (Discord, GitHub – for community-led growth.) ├─ FAQ ├─ Contact Support └─ Contribute (Encourage feedback/shaping the product.) ``` **Content Consolidation:** * Merged separate "Concept" and "Console Guide" files into single, comprehensive **Overview** pages for core resources: * `Organizations`, `Projects`, `Applications`, `Users`, `Console`, and `Actions`. ``` concepts/structure/organizations + guides/manage/console/organizations -> guides/manage/console/organizations-overview concepts/structure/projects + guides/manage/console/projects -> guides/manage/console/projects-overview concepts/structure/applications + guides/manage/console/applications -> guides/manage/console/applications-overview concepts/structure/users + guides/manage/console/users -> guides/manage/console/users-overview guides/manage/console/actions + apis/actions/introduction -> guides/manage/console/actions-overview concepts/features/console + guides/manage/console/overview -> guides/manage/console/console-overview ``` **Redirects (`vercel.json`):** * Added permanent redirects for all the 6 legacy files mentioned above **No files were deleted** --------- Co-authored-by: Florian Forster <florian@zitadel.com>
1 hour ago by yonas
Succeeded
main
c30ab549 Merge 96f9bbc0442f1410ee53f305089659632f5dd78e into 3afa6a2e81a326db5fdcc6ad84d35c5ed0701455
13 hours ago by pull[bot]
Succeeded
main
96f9bbc0 docs: structure update (#11275) ### **Restructure Docs Navigation & Consolidate Core Concepts** **Summary** This PR refactors the documentation navigation to follow a clearer **User Journey** and consolidates fragmented pages to reduce redundancy. **Key Changes** * **Sidebar:** * Replaced the legacy resource-based structure with user-journey-focused categories. **Proposed Structure:** ``` Get Started ├─ Overview │ └─ Guides Overview (Brief intro to docs, persona-aligned: "Get auth working in minutes for your B2B app.") ├─ Quickstart Guide │ └─ Quickstart (Step-by-step: Sign up, spin up instance, connect app, log in – mirrors brand's 4-step guide.) ├─ Authenticate Users │ ├─ Login with ZITADEL (OIDC) │ ├─ Get ID / Access Token │ └─ Logout ├─ Examples & SDKs │ ├─ SPA / Frontend │ ├─ Web Applications │ ├─ APIs / Backend Services │ ├─ Hybrid / Full-Stack │ └─ Sample Applications (Include community-contributed examples for openness.) ├─ Key Concepts │ ├─ Instances, Orgs, Projects, Apps │ ├─ Policies (Intro) │ └─ Users & Roles └─ Use Cases ├─ B2B Integration (Tailored to multi-tenant enterprise needs.) ├─ B2C Login ├─ Multi-Tenant / SaaS ├─ Branded Login & White-Label └─ Machine-to-Machine (M2M) Configure Identity & Policies ├─ Identity Providers │ ├─ External IDPs (e.g., Google, Azure) │ └─ Custom Providers ├─ Policies │ ├─ Password Policies │ ├─ Lockout Policies │ └─ Privacy Policies ├─ Roles & Permissions │ ├─ RBAC Setup │ └─ Custom Roles └─ Compliance & Security ├─ Audits & Logs └─ Certifications (Highlight trust through openness.) Integrate & Authenticate ├─ OIDC & OAuth Flows ├─ API Access │ ├─ gRPC APIs │ └─ REST APIs ├─ SDKs │ ├─ Go │ ├─ JavaScript/TypeScript │ ├─ Python │ └─ Others (Link to community SDKs.) └─ External Integrations ├─ SAML ├─ LDAP └─ Webhooks Test & Debug ├─ Testing Tools │ ├─ Console Testing │ └─ API Playground ├─ Common Issues │ ├─ Token Errors │ └─ Integration Failures └─ Debugging Guides ├─ Logs & Monitoring └─ Error Codes Reference Deploy & Operate ├─ Deployment Options │ ├─ Cloud (ZITADEL Cloud) │ ├─ Self-Hosted (Linux, MacOS) │ ├─ Docker Compose │ └─ Kubernetes ├─ Configuration │ ├─ Environment Variables │ └─ Advanced Settings ├─ Scaling & Performance │ ├─ High Availability │ └─ Backup & Restore └─ Monitoring & Maintenance ├─ Metrics └─ Upgrades Architecture & Concepts ├─ System Architecture │ ├─ Core Components │ └─ Data Flow Diagrams (Expressive visuals per brand.) ├─ Principles │ ├─ Multi-Tenancy │ └─ Open Standards (OIDC, SAML) └─ Advanced Topics ├─ Customization └─ Extensibility (Open-source contributions.) Product, Releases & Support ├─ Product Features │ ├─ Roadmap (Public, for transparency.) │ └─ Pricing & Tiers ├─ Releases │ ├─ Changelog │ └─ Upgrade Guides └─ Support Resources ├─ Community (Discord, GitHub – for community-led growth.) ├─ FAQ ├─ Contact Support └─ Contribute (Encourage feedback/shaping the product.) ``` **Content Consolidation:** * Merged separate "Concept" and "Console Guide" files into single, comprehensive **Overview** pages for core resources: * `Organizations`, `Projects`, `Applications`, `Users`, `Console`, and `Actions`. ``` concepts/structure/organizations + guides/manage/console/organizations -> guides/manage/console/organizations-overview concepts/structure/projects + guides/manage/console/projects -> guides/manage/console/projects-overview concepts/structure/applications + guides/manage/console/applications -> guides/manage/console/applications-overview concepts/structure/users + guides/manage/console/users -> guides/manage/console/users-overview guides/manage/console/actions + apis/actions/introduction -> guides/manage/console/actions-overview concepts/features/console + guides/manage/console/overview -> guides/manage/console/console-overview ``` **Redirects (`vercel.json`):** * Added permanent redirects for all the 6 legacy files mentioned above **No files were deleted** --------- Co-authored-by: Florian Forster <florian@zitadel.com>
13 hours ago by pull[bot]
Succeeded
main
d85c6ff4 Merge 96f9bbc0442f1410ee53f305089659632f5dd78e into 3afa6a2e81a326db5fdcc6ad84d35c5ed0701455
14 hours ago by pull[bot]
Succeeded
main
96f9bbc0 docs: structure update (#11275) ### **Restructure Docs Navigation & Consolidate Core Concepts** **Summary** This PR refactors the documentation navigation to follow a clearer **User Journey** and consolidates fragmented pages to reduce redundancy. **Key Changes** * **Sidebar:** * Replaced the legacy resource-based structure with user-journey-focused categories. **Proposed Structure:** ``` Get Started ├─ Overview │ └─ Guides Overview (Brief intro to docs, persona-aligned: "Get auth working in minutes for your B2B app.") ├─ Quickstart Guide │ └─ Quickstart (Step-by-step: Sign up, spin up instance, connect app, log in – mirrors brand's 4-step guide.) ├─ Authenticate Users │ ├─ Login with ZITADEL (OIDC) │ ├─ Get ID / Access Token │ └─ Logout ├─ Examples & SDKs │ ├─ SPA / Frontend │ ├─ Web Applications │ ├─ APIs / Backend Services │ ├─ Hybrid / Full-Stack │ └─ Sample Applications (Include community-contributed examples for openness.) ├─ Key Concepts │ ├─ Instances, Orgs, Projects, Apps │ ├─ Policies (Intro) │ └─ Users & Roles └─ Use Cases ├─ B2B Integration (Tailored to multi-tenant enterprise needs.) ├─ B2C Login ├─ Multi-Tenant / SaaS ├─ Branded Login & White-Label └─ Machine-to-Machine (M2M) Configure Identity & Policies ├─ Identity Providers │ ├─ External IDPs (e.g., Google, Azure) │ └─ Custom Providers ├─ Policies │ ├─ Password Policies │ ├─ Lockout Policies │ └─ Privacy Policies ├─ Roles & Permissions │ ├─ RBAC Setup │ └─ Custom Roles └─ Compliance & Security ├─ Audits & Logs └─ Certifications (Highlight trust through openness.) Integrate & Authenticate ├─ OIDC & OAuth Flows ├─ API Access │ ├─ gRPC APIs │ └─ REST APIs ├─ SDKs │ ├─ Go │ ├─ JavaScript/TypeScript │ ├─ Python │ └─ Others (Link to community SDKs.) └─ External Integrations ├─ SAML ├─ LDAP └─ Webhooks Test & Debug ├─ Testing Tools │ ├─ Console Testing │ └─ API Playground ├─ Common Issues │ ├─ Token Errors │ └─ Integration Failures └─ Debugging Guides ├─ Logs & Monitoring └─ Error Codes Reference Deploy & Operate ├─ Deployment Options │ ├─ Cloud (ZITADEL Cloud) │ ├─ Self-Hosted (Linux, MacOS) │ ├─ Docker Compose │ └─ Kubernetes ├─ Configuration │ ├─ Environment Variables │ └─ Advanced Settings ├─ Scaling & Performance │ ├─ High Availability │ └─ Backup & Restore └─ Monitoring & Maintenance ├─ Metrics └─ Upgrades Architecture & Concepts ├─ System Architecture │ ├─ Core Components │ └─ Data Flow Diagrams (Expressive visuals per brand.) ├─ Principles │ ├─ Multi-Tenancy │ └─ Open Standards (OIDC, SAML) └─ Advanced Topics ├─ Customization └─ Extensibility (Open-source contributions.) Product, Releases & Support ├─ Product Features │ ├─ Roadmap (Public, for transparency.) │ └─ Pricing & Tiers ├─ Releases │ ├─ Changelog │ └─ Upgrade Guides └─ Support Resources ├─ Community (Discord, GitHub – for community-led growth.) ├─ FAQ ├─ Contact Support └─ Contribute (Encourage feedback/shaping the product.) ``` **Content Consolidation:** * Merged separate "Concept" and "Console Guide" files into single, comprehensive **Overview** pages for core resources: * `Organizations`, `Projects`, `Applications`, `Users`, `Console`, and `Actions`. ``` concepts/structure/organizations + guides/manage/console/organizations -> guides/manage/console/organizations-overview concepts/structure/projects + guides/manage/console/projects -> guides/manage/console/projects-overview concepts/structure/applications + guides/manage/console/applications -> guides/manage/console/applications-overview concepts/structure/users + guides/manage/console/users -> guides/manage/console/users-overview guides/manage/console/actions + apis/actions/introduction -> guides/manage/console/actions-overview concepts/features/console + guides/manage/console/overview -> guides/manage/console/console-overview ``` **Redirects (`vercel.json`):** * Added permanent redirects for all the 6 legacy files mentioned above **No files were deleted** --------- Co-authored-by: Florian Forster <florian@zitadel.com>
14 hours ago by pull[bot]
Succeeded
main
96f9bbc0 docs: structure update (#11275) ### **Restructure Docs Navigation & Consolidate Core Concepts** **Summary** This PR refactors the documentation navigation to follow a clearer **User Journey** and consolidates fragmented pages to reduce redundancy. **Key Changes** * **Sidebar:** * Replaced the legacy resource-based structure with user-journey-focused categories. **Proposed Structure:** ``` Get Started ├─ Overview │ └─ Guides Overview (Brief intro to docs, persona-aligned: "Get auth working in minutes for your B2B app.") ├─ Quickstart Guide │ └─ Quickstart (Step-by-step: Sign up, spin up instance, connect app, log in – mirrors brand's 4-step guide.) ├─ Authenticate Users │ ├─ Login with ZITADEL (OIDC) │ ├─ Get ID / Access Token │ └─ Logout ├─ Examples & SDKs │ ├─ SPA / Frontend │ ├─ Web Applications │ ├─ APIs / Backend Services │ ├─ Hybrid / Full-Stack │ └─ Sample Applications (Include community-contributed examples for openness.) ├─ Key Concepts │ ├─ Instances, Orgs, Projects, Apps │ ├─ Policies (Intro) │ └─ Users & Roles └─ Use Cases ├─ B2B Integration (Tailored to multi-tenant enterprise needs.) ├─ B2C Login ├─ Multi-Tenant / SaaS ├─ Branded Login & White-Label └─ Machine-to-Machine (M2M) Configure Identity & Policies ├─ Identity Providers │ ├─ External IDPs (e.g., Google, Azure) │ └─ Custom Providers ├─ Policies │ ├─ Password Policies │ ├─ Lockout Policies │ └─ Privacy Policies ├─ Roles & Permissions │ ├─ RBAC Setup │ └─ Custom Roles └─ Compliance & Security ├─ Audits & Logs └─ Certifications (Highlight trust through openness.) Integrate & Authenticate ├─ OIDC & OAuth Flows ├─ API Access │ ├─ gRPC APIs │ └─ REST APIs ├─ SDKs │ ├─ Go │ ├─ JavaScript/TypeScript │ ├─ Python │ └─ Others (Link to community SDKs.) └─ External Integrations ├─ SAML ├─ LDAP └─ Webhooks Test & Debug ├─ Testing Tools │ ├─ Console Testing │ └─ API Playground ├─ Common Issues │ ├─ Token Errors │ └─ Integration Failures └─ Debugging Guides ├─ Logs & Monitoring └─ Error Codes Reference Deploy & Operate ├─ Deployment Options │ ├─ Cloud (ZITADEL Cloud) │ ├─ Self-Hosted (Linux, MacOS) │ ├─ Docker Compose │ └─ Kubernetes ├─ Configuration │ ├─ Environment Variables │ └─ Advanced Settings ├─ Scaling & Performance │ ├─ High Availability │ └─ Backup & Restore └─ Monitoring & Maintenance ├─ Metrics └─ Upgrades Architecture & Concepts ├─ System Architecture │ ├─ Core Components │ └─ Data Flow Diagrams (Expressive visuals per brand.) ├─ Principles │ ├─ Multi-Tenancy │ └─ Open Standards (OIDC, SAML) └─ Advanced Topics ├─ Customization └─ Extensibility (Open-source contributions.) Product, Releases & Support ├─ Product Features │ ├─ Roadmap (Public, for transparency.) │ └─ Pricing & Tiers ├─ Releases │ ├─ Changelog │ └─ Upgrade Guides └─ Support Resources ├─ Community (Discord, GitHub – for community-led growth.) ├─ FAQ ├─ Contact Support └─ Contribute (Encourage feedback/shaping the product.) ``` **Content Consolidation:** * Merged separate "Concept" and "Console Guide" files into single, comprehensive **Overview** pages for core resources: * `Organizations`, `Projects`, `Applications`, `Users`, `Console`, and `Actions`. ``` concepts/structure/organizations + guides/manage/console/organizations -> guides/manage/console/organizations-overview concepts/structure/projects + guides/manage/console/projects -> guides/manage/console/projects-overview concepts/structure/applications + guides/manage/console/applications -> guides/manage/console/applications-overview concepts/structure/users + guides/manage/console/users -> guides/manage/console/users-overview guides/manage/console/actions + apis/actions/introduction -> guides/manage/console/actions-overview concepts/features/console + guides/manage/console/overview -> guides/manage/console/console-overview ``` **Redirects (`vercel.json`):** * Added permanent redirects for all the 6 legacy files mentioned above **No files were deleted** --------- Co-authored-by: Florian Forster <florian@zitadel.com>
14 hours ago by pull[bot]
Succeeded
main
d8e1a46e Merge 96f9bbc0442f1410ee53f305089659632f5dd78e into 3afa6a2e81a326db5fdcc6ad84d35c5ed0701455
14 hours ago by pull[bot]
Succeeded
main
96f9bbc0 docs: structure update (#11275) ### **Restructure Docs Navigation & Consolidate Core Concepts** **Summary** This PR refactors the documentation navigation to follow a clearer **User Journey** and consolidates fragmented pages to reduce redundancy. **Key Changes** * **Sidebar:** * Replaced the legacy resource-based structure with user-journey-focused categories. **Proposed Structure:** ``` Get Started ├─ Overview │ └─ Guides Overview (Brief intro to docs, persona-aligned: "Get auth working in minutes for your B2B app.") ├─ Quickstart Guide │ └─ Quickstart (Step-by-step: Sign up, spin up instance, connect app, log in – mirrors brand's 4-step guide.) ├─ Authenticate Users │ ├─ Login with ZITADEL (OIDC) │ ├─ Get ID / Access Token │ └─ Logout ├─ Examples & SDKs │ ├─ SPA / Frontend │ ├─ Web Applications │ ├─ APIs / Backend Services │ ├─ Hybrid / Full-Stack │ └─ Sample Applications (Include community-contributed examples for openness.) ├─ Key Concepts │ ├─ Instances, Orgs, Projects, Apps │ ├─ Policies (Intro) │ └─ Users & Roles └─ Use Cases ├─ B2B Integration (Tailored to multi-tenant enterprise needs.) ├─ B2C Login ├─ Multi-Tenant / SaaS ├─ Branded Login & White-Label └─ Machine-to-Machine (M2M) Configure Identity & Policies ├─ Identity Providers │ ├─ External IDPs (e.g., Google, Azure) │ └─ Custom Providers ├─ Policies │ ├─ Password Policies │ ├─ Lockout Policies │ └─ Privacy Policies ├─ Roles & Permissions │ ├─ RBAC Setup │ └─ Custom Roles └─ Compliance & Security ├─ Audits & Logs └─ Certifications (Highlight trust through openness.) Integrate & Authenticate ├─ OIDC & OAuth Flows ├─ API Access │ ├─ gRPC APIs │ └─ REST APIs ├─ SDKs │ ├─ Go │ ├─ JavaScript/TypeScript │ ├─ Python │ └─ Others (Link to community SDKs.) └─ External Integrations ├─ SAML ├─ LDAP └─ Webhooks Test & Debug ├─ Testing Tools │ ├─ Console Testing │ └─ API Playground ├─ Common Issues │ ├─ Token Errors │ └─ Integration Failures └─ Debugging Guides ├─ Logs & Monitoring └─ Error Codes Reference Deploy & Operate ├─ Deployment Options │ ├─ Cloud (ZITADEL Cloud) │ ├─ Self-Hosted (Linux, MacOS) │ ├─ Docker Compose │ └─ Kubernetes ├─ Configuration │ ├─ Environment Variables │ └─ Advanced Settings ├─ Scaling & Performance │ ├─ High Availability │ └─ Backup & Restore └─ Monitoring & Maintenance ├─ Metrics └─ Upgrades Architecture & Concepts ├─ System Architecture │ ├─ Core Components │ └─ Data Flow Diagrams (Expressive visuals per brand.) ├─ Principles │ ├─ Multi-Tenancy │ └─ Open Standards (OIDC, SAML) └─ Advanced Topics ├─ Customization └─ Extensibility (Open-source contributions.) Product, Releases & Support ├─ Product Features │ ├─ Roadmap (Public, for transparency.) │ └─ Pricing & Tiers ├─ Releases │ ├─ Changelog │ └─ Upgrade Guides └─ Support Resources ├─ Community (Discord, GitHub – for community-led growth.) ├─ FAQ ├─ Contact Support └─ Contribute (Encourage feedback/shaping the product.) ``` **Content Consolidation:** * Merged separate "Concept" and "Console Guide" files into single, comprehensive **Overview** pages for core resources: * `Organizations`, `Projects`, `Applications`, `Users`, `Console`, and `Actions`. ``` concepts/structure/organizations + guides/manage/console/organizations -> guides/manage/console/organizations-overview concepts/structure/projects + guides/manage/console/projects -> guides/manage/console/projects-overview concepts/structure/applications + guides/manage/console/applications -> guides/manage/console/applications-overview concepts/structure/users + guides/manage/console/users -> guides/manage/console/users-overview guides/manage/console/actions + apis/actions/introduction -> guides/manage/console/actions-overview concepts/features/console + guides/manage/console/overview -> guides/manage/console/console-overview ``` **Redirects (`vercel.json`):** * Added permanent redirects for all the 6 legacy files mentioned above **No files were deleted** --------- Co-authored-by: Florian Forster <florian@zitadel.com>
16 hours ago by fcoppede
Succeeded
main
16 hours ago
Succeeded
main
bc6f945d Merge 686de9996788f24b77f555b19adf7bfdd66644b3 into 4b5d6e39e195ecefb8b5382e3d2460ef70d6a980
24 hours ago by pull[bot]
Succeeded
main
3afa6a2e docs: correct "complement" flow names (#11320) # Which Problems Are Solved As part of the naming inconsistencies (#5888) we want to ensure action v1 flow name are always correct and mapping to enum values line up: #11309 # How the Problems Are Solved Rename last "Customize SAML Response" occurrences to "Complement SAML Response" where it's referring to the flow type. There are some titles left with "customize SAML / OIDC response", which refer to the intent of customizing the outcome and not directly to the flow type. # Additional Changes None # Additional Context - closes 11309
1 day ago by yonas
Succeeded
main
267f2049 Merge 686de9996788f24b77f555b19adf7bfdd66644b3 into 4b5d6e39e195ecefb8b5382e3d2460ef70d6a980
1 day ago by pull[bot]
Succeeded
main
686de999 fix(cmd/build): populate date variable when not set through ldflags (#11316) # Which Problems Are Solved When building zitadel through `go build` or using an IDE debugging tool, ldflags are not passed by dedault. In the past this was taken care of by the `make compile` command, which got replaced by NX. The `nx @zitadel/api:build` command does not set the ldflags either. Only the `pack-platform` command does. Because the ldflags aren't passed, the `date` and other variables remain empty in the `cmd/build` package. During init of the package, if the `version` is empty it defaults to the `date` variable. When the `date` field was empty, the parsed `dateTime` would default to `time.Now()`, but the `date` variable remained empty, resulting in a empty version. A consistently empty version string prevents upgrades of projections on dev systems, as the version from the last run is used. # How the Problems Are Solved If date failed to parse and `dateTime` is set to Now, use the formated string of `dateTime` as `date`. # Additional Context - Blocks https://github.com/zitadel/zitadel/pull/11239
1 day ago by pull[bot]
Succeeded
main
2 days ago
Succeeded
main
686de999 fix(cmd/build): populate date variable when not set through ldflags (#11316) # Which Problems Are Solved When building zitadel through `go build` or using an IDE debugging tool, ldflags are not passed by dedault. In the past this was taken care of by the `make compile` command, which got replaced by NX. The `nx @zitadel/api:build` command does not set the ldflags either. Only the `pack-platform` command does. Because the ldflags aren't passed, the `date` and other variables remain empty in the `cmd/build` package. During init of the package, if the `version` is empty it defaults to the `date` variable. When the `date` field was empty, the parsed `dateTime` would default to `time.Now()`, but the `date` variable remained empty, resulting in a empty version. A consistently empty version string prevents upgrades of projections on dev systems, as the version from the last run is used. # How the Problems Are Solved If date failed to parse and `dateTime` is set to Now, use the formated string of `dateTime` as `date`. # Additional Context - Blocks https://github.com/zitadel/zitadel/pull/11239
2 days ago by mdarii
Succeeded
main
0e360d60 Merge 686de9996788f24b77f555b19adf7bfdd66644b3 into 4b5d6e39e195ecefb8b5382e3d2460ef70d6a980
2 days ago by pull[bot]
Succeeded
main
686de999 fix(cmd/build): populate date variable when not set through ldflags (#11316) # Which Problems Are Solved When building zitadel through `go build` or using an IDE debugging tool, ldflags are not passed by dedault. In the past this was taken care of by the `make compile` command, which got replaced by NX. The `nx @zitadel/api:build` command does not set the ldflags either. Only the `pack-platform` command does. Because the ldflags aren't passed, the `date` and other variables remain empty in the `cmd/build` package. During init of the package, if the `version` is empty it defaults to the `date` variable. When the `date` field was empty, the parsed `dateTime` would default to `time.Now()`, but the `date` variable remained empty, resulting in a empty version. A consistently empty version string prevents upgrades of projections on dev systems, as the version from the last run is used. # How the Problems Are Solved If date failed to parse and `dateTime` is set to Now, use the formated string of `dateTime` as `date`. # Additional Context - Blocks https://github.com/zitadel/zitadel/pull/11239
2 days ago by pull[bot]
Succeeded
main
2 days ago
Succeeded
main
686de999 fix(cmd/build): populate date variable when not set through ldflags (#11316) # Which Problems Are Solved When building zitadel through `go build` or using an IDE debugging tool, ldflags are not passed by dedault. In the past this was taken care of by the `make compile` command, which got replaced by NX. The `nx @zitadel/api:build` command does not set the ldflags either. Only the `pack-platform` command does. Because the ldflags aren't passed, the `date` and other variables remain empty in the `cmd/build` package. During init of the package, if the `version` is empty it defaults to the `date` variable. When the `date` field was empty, the parsed `dateTime` would default to `time.Now()`, but the `date` variable remained empty, resulting in a empty version. A consistently empty version string prevents upgrades of projections on dev systems, as the version from the last run is used. # How the Problems Are Solved If date failed to parse and `dateTime` is set to Now, use the formated string of `dateTime` as `date`. # Additional Context - Blocks https://github.com/zitadel/zitadel/pull/11239
2 days ago by pull[bot]
Succeeded
main
6d8f81a6 Merge 686de9996788f24b77f555b19adf7bfdd66644b3 into 4b5d6e39e195ecefb8b5382e3d2460ef70d6a980
2 days ago by pull[bot]