@astrale-domains/services 0.4.0 → 0.4.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,20 @@
1
1
  # Changelog
2
2
 
3
+ ## [0.4.2](https://github.com/astrale-os/domains/compare/services-v0.4.1...services-v0.4.2) (2026-09-07)
4
+
5
+
6
+ ### Bug Fixes
7
+
8
+ * **services:** report active deletion conflicts ([#195](https://github.com/astrale-os/domains/issues/195)) ([11622fa](https://github.com/astrale-os/domains/commit/11622fa9d52e30f54083d34d4f21aacf1e30490c))
9
+
10
+ ## [0.4.1](https://github.com/astrale-os/domains/compare/services-v0.4.0...services-v0.4.1) (2026-09-07)
11
+
12
+
13
+ ### Bug Fixes
14
+
15
+ * **schema:** infer domain schemas with the released SDK ([#189](https://github.com/astrale-os/domains/issues/189)) ([c6198a1](https://github.com/astrale-os/domains/commit/c6198a188ed97ea747419e5a3367faf5839c3ba4))
16
+ * **services:** preserve ready deployment after rejected update ([#193](https://github.com/astrale-os/domains/issues/193)) ([e99f509](https://github.com/astrale-os/domains/commit/e99f509ff389ace288583ffc37d9f7d7f1003ae2))
17
+
3
18
  ## [0.4.0](https://github.com/astrale-os/domains/compare/services-v0.3.4...services-v0.4.0) (2026-09-07)
4
19
 
5
20
 
package/README.md CHANGED
@@ -97,3 +97,11 @@ until its retained operation lease expires (currently 30 minutes from acquisitio
97
97
  Retry the same deployment after the expiry reported in the rejection; it reuses the Service and
98
98
  provider identity. Do not clear the lease or create another Service to bypass an uncertain outcome.
99
99
  An operation without a recorded expiry needs operator inspection, not a guessed retry deadline.
100
+
101
+ A definitively rejected update restores a previously ready Service only when the Provider observes
102
+ the same serving script digest and tenant routing coordinates. The restoration is atomic and fenced
103
+ by the current operation receipt; it restores the previous name and description and clears the
104
+ rejected attempt. The deployment still returns a rejection, but the retained Service remains
105
+ manageable. Failed creations, uncertain outcomes, mismatched observations, and unresolved previous
106
+ attempts remain failed rather than claiming that the old deployment is ready. This verification adds
107
+ no provider request to a successful deployment.