Fix links in source and markdown files

Author: sophokles73

.github/workflows/README.md

@@ -8,9 +8,9 @@ At this time, there are three events that will initiate a workflow run:
 
 ## PRs and merges to main
 
-We want a comprehensive but also quick check&test workflow. This should be testing all relevant/obvious feature sets, run on all major OSes, and of course include all the Rust goodness around cargo check, fmt, clippy and so on.
+We want a comprehensive but also quick check & test workflow. This should be testing all relevant/obvious feature sets, run on all major OSes, and of course include all the Rust goodness around cargo check, fmt, clippy and so on.
 
-This is implemented in [`check.yaml`](check.yaml)
+This is implemented in [`check.yaml`](check.yaml) and [`check-dependencies.yaml`](check-dependencies.yaml)
 
 ## Release publication
 
@@ -24,17 +24,12 @@ All the tests we can think of, however long they might take. For instance, we ca
 
 This is implemented in [`nightly.yaml`](nightly.yaml)
 
+## uProtocol specification compatibility
+
+The uProtocol specification is evolving over time. In order to discover any discrepancies between the currently implemented version and the changes being introduced to the specification, we perform a nightly check that verifies if the current up-rust code base on the main branch can be compiled and test can be run successfully using the most recent revision of the uProtocol specification.
+
+This is implemented in [`latest-up-spec-compatibility.yaml`](latest-up-spec-compatibility.yaml)
+
 ## Further workflow modules
 
-In addition to the main workflows described above, there exist a number of modules that are used by these main workflows. They can also be run standalone, and are intendet to make composing the capabilities of our main workflows simpler. These are:
-
-- [`check-up-spec-compatibility.yaml`](check-up-spec-compatibility.yaml) - checks if the current main branch can be built against up-spec's main branch instead of its latest tag/release
-- [`coverage.yaml`](coverage.yaml) - collects test code coverage, and can optionally upload the results to codecov.io
-  - Will publish coverage data to CodeCov if `${{ secrets.CODECOV_TOKEN }}` is set
-  - outputs: download URL for the workflow-generated coverage info file
-- [`license-report.yaml`](license-report.yaml) - create a license report for `up-rust` and all its dependencies in html format
-  - outputs: download URL for the workflow-generated license report
-- [`requirements-tracing.yaml`](requirements-tracing.yaml) - Run OpenFastTrace to verify that all requirements from uProtocol Specification are met
-- [`test-featurematrix.yaml`](test-featurematrix.yaml) - Test all feature combinations on a range of OS platforms
-- [`verify-msrv.yaml`](verify-msrv.yaml) - checks if the MSRV ('Minimum Supported Rust Version) declared in Cargo.toml is correct
-- [`x-build.yaml`](x-build.yaml) - Run release builds on multiple architecture targets
+In addition to the main workflows described above, there exist a number of modules that are used by these main workflows. These live in the [uProtocol CI/CD repository](https://github.com/eclipse-uprotocol/ci-cd)

CONTRIBUTING.md

@@ -16,18 +16,15 @@ The project maintains the following source code repositories
 ## Eclipse Contributor Agreement
 
 Before your contribution can be accepted by the project team contributors must
-electronically sign the Eclipse Contributor Agreement (ECA).
-
-<http://www.eclipse.org/legal/ECA.php>
+electronically sign the [Eclipse Contributor Agreement](https://www.eclipse.org/legal/ECA.php) (ECA).
 
 Commits that are provided by non-committers must have a Signed-off-by field in
 the footer indicating that the author is aware of the terms by which the
 contribution has been provided to the project. The non-committer must
 additionally have an Eclipse Foundation account and must have a signed Eclipse
 Contributor Agreement (ECA) on file.
 
-For more information, please see the Eclipse Committer Handbook:
-<https://www.eclipse.org/projects/handbook/#resources-commit>
+For more information, please see the [Eclipse Committer Handbook](https://www.eclipse.org/projects/handbook/#resources-commit).
 
 ## Setting up a development environment
 

Cargo.lock

@@ -30,7 +30,7 @@ name = "up-rust"
 readme = "README.md"
 repository = "https://github.com/eclipse-uprotocol/up-rust"
 rust-version = "1.82"
-version = "0.5.0"
+version = "0.6.0"
 
 [features]
 default = ["communication"]

Cargo.toml

@@ -192,7 +192,7 @@
    you may not use this file except in compliance with the License.
    You may obtain a copy of the License at
 
-       http://www.apache.org/licenses/LICENSE-2.0
+       https://www.apache.org/licenses/LICENSE-2.0
 
    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,

LICENSE

@@ -7,7 +7,7 @@
 // you may not use this file except in compliance with the License.
 // You may obtain a copy of the License at
 //
-//     http://www.apache.org/licenses/LICENSE-2.0
+//     https://www.apache.org/licenses/LICENSE-2.0
 //
 // Unless required by applicable law or agreed to in writing, software
 // distributed under the License is distributed on an "AS IS" BASIS,

src/cloudevents.rs

@@ -164,7 +164,7 @@ mod tests {
     // [utest->req~ustatus-data-model-impl~1]
     fn test_ustatus_fail_with_code() {
         let details = vec![Any {
-            type_url: "https://google.com/timestamp".to_string(),
+            type_url: "type.googleapis.com/google.protobuf.Timestamp".to_string(),
             ..Default::default()
         }];
         UCode::VALUES.iter().for_each(|code| {
@@ -185,7 +185,7 @@ mod tests {
             code: UCode::CANCELLED.into(),
             message: Some("the message".to_string()),
             details: vec![Any {
-                type_url: "https://google.com/timestamp".to_string(),
+                type_url: "type.googleapis.com/google.protobuf.Timestamp".to_string(),
                 ..Default::default()
             }],
             ..Default::default()