You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,10 @@ Apache Polaris 1.1.0-incubating was released on September 19th, 2025.
107
107
ON CONFLICT (version_key) DO UPDATE
108
108
SET version_value =EXCLUDED.version_value;
109
109
COMMENT ON TABLE version IS 'the version of the JDBC schema in use';
110
+
111
+
ALTERTABLEpolaris_schema.entities ADD COLUMN IF NOT EXISTS location_without_scheme TEXT;
110
112
```
113
+
- Please don't enable [OPTIMIZED_SIBLING_CHECK](https://github.com/apache/polaris/blob/740993963cb41c2c1b4638be5e04dd00f1263c98/polaris-core/src/main/java/org/apache/polaris/core/config/FeatureConfiguration.java#L346) feature configuration, once the above SQL statements are run. As it may lead to incorrect behavior, due to missing data for location_without_scheme column.
111
114
- **Deprecations**
112
115
- The property `polaris.active-roles-provider.type` is deprecated for removal.
113
116
- The `ActiveRolesProvider` interface is deprecated for removal.
CI builds originating from the `apache/polaris` repository will have access to the Apache organization-level secret
182
-
`DEVELOCITY_ACCESS_KEY` and publish build scans using the secret. CI builds originating from pull requests from forks
183
-
will not have access to the secret and will silently skip build scan publication.
184
-
185
-
Apache committers can publish build scans from their local machine by
186
-
[provisioning an access key](https://docs.gradle.com/develocity/gradle-plugin/current/#automated_access_key_provisioning)
187
-
using ASF LDAP credentials. Builds by anonymous, unauthenticated contributors will silently skip build scan publication.
178
+
Build scans of CI builds from a branch or tag in the `apache/polaris` repository on GitHub publish build scans
179
+
to the ASF Develocity instance at
180
+
[develocity.apache.org](https://develocity.apache.org/scans?search.rootProjectNames=polaris), if the workflow runs have access to the Apache organization-level secret
181
+
`DEVELOCITY_ACCESS_KEY`.
182
+
183
+
Build scans of local developer builds publish build scans only if the Gradle command line option `--scan` is used.
184
+
Those build scans are published to Gradle's public Develocity instance (see advanced configuration options below).
185
+
Note that build scans on Gradle's public Develocity instance are publicly accessible to anyone.
186
+
You have to accept Gradle's terms of service to publish to the Gradle's public Develocity instance.
187
+
188
+
CI builds originating from pull requests against the `apache/polaris` GitHub repository are published to Gradle's
189
+
_public_ Develocity instance.
190
+
191
+
Other CI build scans do only publish build scans to the Gradle's _public_ Develocity instance, if the environment
192
+
variable `GRADLE_TOS_ACCEPTED` is set to `true`.
193
+
By setting this variable you agree to the [Gradle's terms of service](https://gradle.com/terms-of-service), because
194
+
accepting these ToS is your personal decision.
195
+
You can configure this environment variable for your GitHub repository in the GitHub repository settings under
196
+
`Secrets` > `Secrets and variables` > `Actions` > choose the `Variables` tab > `New repository variable`.
197
+
198
+
Advanced configuration options for publishing build scans (only local and non-`apache/polaris` repository CI):
199
+
* The project ID published with the build scan can be specified using the environment variable `DEVELOCITY_PROJECT_ID`.
200
+
The project ID defaults to the GitHub repository owner/name, for example `octocat/polaris`.
201
+
* The Develocity server can be specified using the environment variable `DEVELOCITY_SERVER` if build scans should be
202
+
published to another than Gradle's public Develocity instance.
203
+
* If you have to publish build scans to your own Develocity instance, you can configure the access key using a
0 commit comments