Sameera Jayasoma

Yes, this is not a bug. I am closing this issue. Please create a new issue with a proposal.

Considering recent issues/warnings, I now believe that we should suppress compile-time warnings generated by package dependencies. We decided to allow all such warnings a few years ago, but the situation...

IMO, having two different annotations is not good. There is a usability issue here. We seem to be coming up with another annotation-like service contract due to compiler limitations.

Here is the updated semantics of `bal pull` based on this discussion: `bal pull []` - If the package is given, pull its direct and indirect dependencies. - If the...

Yeah, we need to address the module-specific metadata issue.

> +1 for the suggestion, I also think it will be a cleaner approach. > > For module summary we extract the summary from Module.md if so there is bit...

Related: https://github.com/ballerina-platform/ballerina-spec/issues/982#issuecomment-1911204336

If you, as the package author, had to mark the latest patch version of a package as deprecated, we recommend pushing a new version as soon as possible.

I can think of two ways to mark a package as deprecated: - Via the Ballerina central UI (This will only work with Ballerina central) - The more general approach...

@chalitha1989, I would immediately revoke the secrets. I am not suggesting deleting the package. Once published, it'll be there forever :)