# January 2026

{% updates format="full" %}
{% update date="2026-01-07" %}

## Source to Blueprint

This release focuses on streamlining blueprint composition directly from source, improving cloud account visibility, and enhancing infrastructure-as-code (IaC) processing for more reliable deployments.

#### 🚀 New Features

**In-Line Blueprint Creation from Source**

You can now add new packages directly from a Git source during the blueprint composition flow. This includes a dedicated "New package" flow that lets you select a technology, enter Git sources, and manage metadata without leaving the blueprint page.

**What does it mean for you?**

A much faster authoring experience. You no longer need to pre-register packages; you can pull them into your blueprint on the fly, with the system intelligently pre-filling details and persisting sources after publishing.

#### ⚡ Improvements

**Improved Log Storage and Retrieval**

To improve performance and scalability, deployment logs now use a more performant storage layer. Log retrieval is faster and more reliable, while maintaining full backward compatibility with older logs.

**Accurate Child Package Metadata**

We've enriched the blueprint format to preserve child package metadata during processing. This ensures that even if you override output names, outputs for artifact-published packages are accurately tracked and displayed.

**Unified Cloud Account Visibility**

We've aligned the display of Discovery and Orchestration accounts across the entire platform. Whether you are in the Environment table, the Graph view, or Account Settings, the labeling and modal behavior are now consistent.

**Standardized Blueprint Terminology & Options**

* **Terminology Update**: You can now "View manifest" to see your `bricks.yaml` or `bricks.json` directly, using clearer and more consistent product language throughout.
* **Action Consolidation:** Blueprint actions are now normalized across the app, replacing multiple "Review" variations with a single, clear "Review deployment" entry point.
* **Plan Page Clarity:** The "Deployer" label on the Plan page has been updated to "Initiated by" to more accurately reflect the user who started the run.

**Modernized Job Scheduling**

The job scheduler has been improved for greater reliability. Schedule changes are now persisted immediately, and recovery from interruptions is faster and more robust.

**Security Enhancements**

* Cloud to Code agent calls now support authenticated callbacks, enhancing security for import and generation flows.

#### 🐛 Bug Fixes

**Consistent Deployment State Locations**

Fixed an issue where state files were occasionally created in the incorrect directory during the Plan phase. All state and backup files are now stored in consistent, predictable locations for reliable deployments.

**Duplicate Prop Key Consolidation**

Duplicate prop keys across multiple packages are now correctly identified and mapped to a single input, preventing cluttered forms and redundant data entry.

**Members List & Pagination Reliability**

Resolved an issue that occurred when navigating the members list if a user record was missing an email address. Pagination now works reliably across all user sets.

**UI & Layout Fixes**

* Zoom Accessibility: Fixed the Environment page cost block so it remains fully accessible and readable even when browser zoom is increased.
* Avatar Alignment: Standardized creator avatars to 24x24 pixels across the Deployment, Plan, and Environment pages for better visual hierarchy.
* Packages Sorting: Fixed the "Published by" column in the Packages table to correctly sort by the most recent timestamp.
* Empty State Interactions: Removed a broken "Edit input" action that appeared in empty deployment states, preventing the modal from closing prematurely.<br>
  {% endupdate %}

{% update date="2026-01-01" %}

## Connect. Import. Accelerate.

This release introduces native Slack and GitHub integrations, a powerful new "Cloud to Code" import workflow, and significant performance enhancements to our cloud discovery and deployment engines.

#### 🚀 New Features

**Slack Integration**

We've enabled comprehensive [Slack integration](https://bluebricks.co/docs/integrations/slack) management [directly within Bluebricks](https://app.bluebricks.co/settings?tab=integrations-slack). This includes OAuth-based connectivity, organization-level enablement, and the ability to trigger interactive actions directly from Slack messages.

**What does it mean for you?**

Streamline your workflows with real-time deployment notifications and take action without leaving your Slack workspace.

<figure><img src="/files/WlHarghkchNgaqIHsYzd" alt=""><figcaption></figcaption></figure>

**GitHub Integration**

A new [GitHub integration](https://bluebricks.co/docs/integrations/github) is now available under [Account Settings](https://app.bluebricks.co/settings?tab=integrations-github). This feature includes a dedicated management page to connect your GitHub organizations and view all connected repositories.

**What does it mean for you?**

Easily link your source code providers to Bluebricks, providing better visibility and a tighter connection between your repositories and managed blueprints.

<figure><img src="/files/O6FwbUOnkDWBpCCiEOBm" alt=""><figcaption></figcaption></figure>

**Cloud to Code: Automated Blueprint Import**

We've introduced a new workflow that transforms discovered cloud resources into managed Blueprints. The process performs deep discovery and streams real-time status and logs back to the UI.

**What does it mean for you?**

Significantly reduce the time spent on manualizing existing infrastructure. You can now import live cloud resources and turn them into version-controlled Bluebricks packages with full visibility into the import process.

#### ⚡ Improvements

**Add from Source (Artifactless Projects)**

You can now register packages directly from a raw source string. The system automatically detects the IaC type, clones the repository, and processes the package via bricks.yaml. If no blueprint file exists, it uses intelligent auto-detection to publish the package.

**What does it mean for you?**

A smoother onboarding experience for existing codebases, allowing you to bring in raw source code and let Bluebricks handle the complexity of packaging and publishing.

**Scalable Cloud Discovery Runtime**

We've re-engineered our discovery engine for better scalability and tenant isolation. This update includes dynamic configuration refreshing, ensuring that provider connections are always up-to-date for better performance.

**Proactive Infrastructure Monitoring**

We've added proactive monitoring to detect and mitigate potential performance issues before they impact your experience.

#### 🐛 Bug Fixes

**Reliable Apply Artifacts**

Fixed an issue where deployment state files were generated in inconsistent locations. State files are now correctly placed alongside the deployment graph, ensuring consistent output and more reliable state management.

**Prevent Duplicate "Approve & Apply" Submissions**

Added client-side protections to prevent multiple approval requests caused by accidental double-clicking. This ensures a cleaner audit trail and prevents redundant deployment executions.

**Accurate Deployment Metadata**

Resolved a UI bug where the deployment overview would sometimes show the most recent activity user instead of the original deployment creator. The overview now accurately reflects who initiated the deployment and when.

**Environment Duplication Fix**

Fixed a bug in the environment setup flow where using shared discovery or execution roles could result in the creation of redundant, duplicate environments.

**Enhanced Validation for Complex Input Types**

Added validation feedback for complex property types, including maps, lists, and tuples. This prevents silent errors by ensuring all required complex inputs are valid before you hit deploy.
{% endupdate %}
{% endupdates %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://bluebricks.co/docs/changelog/january-2026.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.